Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Webapp manifest validator does not support Server Name Indication

VERIFIED FIXED in 2013-11-19


4 years ago
4 years ago


(Reporter: Fabian Köster, Assigned: mat)


Dependency tree / graph



(2 attachments)



4 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31

Steps to reproduce:

I created a simple manifest file
which is delivered with the correct mime-type and defines a launch-path '/' and some icons which are all perfectly accessable.

I tried to submit the webapp into marketplace.

Actual results:

The validator fails with the following output:

Error while requesting icon
Fehler: A remote resource was requested, but an error prevented the request from completing. This may include connection, DNS, or HTTP issues.
Requested resource:

Expected results:

I do not see why it fails. The servers log show only one access for the manifest, but no following requests. I therefore think the validator is broken.

Even if there is a problem with my manifest or webserver I cannot fix it because the validator does not give detailed information about the problem.

Comment 1

4 years ago
Created attachment 753031 [details]
The failing webapp manifest

Comment 2

4 years ago
Created attachment 753034 [details]
Wget succeeds downloading files

I also attach a log showing that my client can retrieve the files using wget without problems.
I tried this out and it's failing the same way for me. I'm not sure why though. The icon is accessible.
Ever confirmed: true

Comment 4

4 years ago
requests.exceptions.SSLError: hostname '' doesn't match either of '', ''

The SSL errors with the domain are causing this error. This error is seen with python-requests 1.2.3.

> import requests
> requests.get('')

At first, the request hung but now it consistently fails with SSL verification errors.
Last Resolved: 4 years ago
Resolution: --- → INVALID

Comment 5

4 years ago
Matt, thank you very much for explaining the cause of this error!

I am not okay with closing this bug as 'invalid', though. For two reasons:

1.) The cause of the problem seems to be that python-requests does not correctly work with VirtualHosts (multiple domain names on same IP). Other http clients (like Chromium, Firefox, wget, ...) do not have this problem and use the correct ssl certificate for this site. I think the webapp validator should also work with vhosts and the bug in python-requests should be fixed (i will search for an upstream fix).

2.) The webapp validator should forward the error message you gave me to the user and until the python-requests bug is fixed should say "vhosts are not supported yet".

Kind regards,

Comment 6

4 years ago
I just noticed the assignment of ssl certificates to virtual host domain names is called "Server Name Indication".
Summary: Webapp manifest validator fails without reason → Webapp manifest validator does not support Server Name Indication

Comment 7

4 years ago
I just found the issue upstream in python-requests:

Comment 8

4 years ago
As a workaround I changed the default certificate to the one for, now the validation succeeds.
Thanks for digging up that commit. It looks like the validator actually uses the version of requests that support this but we seem to hit this error (which is caught and swallowed by requests):

>>> from requests.packages.urllib3.contrib import pyopenssl
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/kumar/tmp/app-validator-env2/lib/python2.6/site-packages/requests/packages/urllib3/contrib/", line 23, in <module>
    from ndg.httpsclient.ssl_peer_verification import (ServerSSLCertVerification,
ImportError: No module named ndg.httpsclient.ssl_peer_verification

We just need some more modules. Basta, r?

Zamboni's prod/compiled requirements will need to be fixed up too. 

We should fix this but P2 since there is a workaround.
Assignee: nobody → kumar.mcmillan
Priority: -- → P3
Resolution: INVALID → ---
Target Milestone: --- → 2013-07-18
Fixed in the validator:

Zamboni patches coming next...
we'll need to wait on bug 892654 until we can deploy this
Depends on: 892654
Target Milestone: 2013-07-18 → ---
hmm, this introduces a regression when trying to connect to the BrowserID verifier service.

15:16:40 django_browserid.base:INFO Verification URL: :/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/django_browserid/
15:16:40 requests.packages.urllib3.connectionpool:INFO Starting new HTTPS connection (1): :/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/requests/packages/urllib3/
Traceback (most recent call last):
  File "/usr/local/Cellar/python26/2.6.8/lib/python2.6/wsgiref/", line 93, in run
    self.result = application(self.environ, self.start_response)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/django/contrib/staticfiles/", line 67, in __call__
    return self.application(environ, start_response)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/django/core/handlers/", line 241, in __call__
    response = self.get_response(request)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/django/core/handlers/", line 179, in get_response
    response = self.handle_uncaught_exception(request, resolver, sys.exc_info())
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/django/core/handlers/", line 111, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/django/views/decorators/", line 77, in wrapped_view
    return view_func(*args, **kwargs)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/tastypie/", line 192, in wrapper
    response = callback(request, *args, **kwargs)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/tastypie/", line 397, in dispatch_list
    return self.dispatch('list', request, **kwargs)
  File "/Users/kumar/dev/zamboni/mkt/api/", line 96, in dispatch
    .dispatch(request_type, request, **kwargs))
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/tastypie/", line 427, in dispatch
    response = method(request, **kwargs)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/tastypie/", line 1165, in post_list
    updated_bundle = self.obj_create(bundle, request=request, **self.remove_api_resource_names(kwargs))
  File "/Users/kumar/dev/zamboni/mkt/account/", line 132, in obj_create'is_native', False)
  File "/Users/kumar/dev/zamboni/apps/users/", line 334, in browserid_authenticate
    url=url, extra_params=extra_params)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/django_browserid/", line 149, in verify
    result = _verify_http_request(url, args)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/django_browserid/", line 86, in _verify_http_request
    r =, **parameters)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/requests/", line 88, in post
    return request('post', url, data=data, **kwargs)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/requests/", line 44, in request
    return session.request(method=method, url=url, **kwargs)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/requests/", line 335, in request
    resp = self.send(prep, **send_kwargs)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/requests/", line 438, in send
    r = adapter.send(request, **kwargs)
  File "/Users/kumar/.virtualenvs/zamboni/lib/python2.6/site-packages/requests/", line 331, in send
    raise SSLError(e)
SSLError: [Errno bad handshake]

I don't understand why. OpenSSL on Mac is outdated (0.98) but even after I rebuilt PyOpenSSL with the 1.01 lib I saw the same problem.
work in progress:
ashort says this may be a bug in requests. If so, we may need to get a patch upstream.
Testing this locally, I encountered the issue described here:

Changes to django-browserid result in a slightly different traceback than the above, but the call it makes results in a SSLError(SSLError(SSLError('bad handshake', WantReadError()),),) exception.

This will require fixing PyOpenSSL support in urllib3 and requests.
Blocks: 826960


4 years ago
Duplicate of this bug: 933755

Comment 17

4 years ago
Any update on this? Can we get this done now?

Comment 18

4 years ago
According to the requests issue mentioned in #comment 15:
>> The changes in shazow/urllib3#233 (now pulled into urllib3 master) fix the issue for me (SSLError('bad handshake', WantReadError())) which occurred for some urls, some times, in some configurations. Can we get this pulled into requests master?
> We'll pull in an up-to-date version into Requests when we release 2.0. =)

requests 2.0.1 is out now, so it's worth upgrading locally and check if we can still reproduce the issue we had with 1.2.3.
Any update on this? This seems to block a few submissions including partners.

Comment 20

4 years ago
requests 2.0.1 is broken in an horrible way (can't even install) :

2.0.0 seems to work though, but I'd need a manifest hosted on a server needing SNI to be sure. Does anyone have a manifest URL that doesn't currently work in production ?
Assignee: kumar.mcmillan → mpillard
Priority: P3 → P2

Comment 21

4 years ago
Please use this manifest to test:

Comment 22

4 years ago
classicning@ : that server doesn't seem to be using SNI ? At first glance it looks like there is an unrelated icon problem (icon size mismatch)

:digitarald : can you give me a manifest from a partner that is blocked by this bug ?
Flags: needinfo?(hkirschner)
Target Milestone: --- → 2013-11-19
The delicious URL reflects the issue discussed here. The validation doesn't fail with the icon mismatch but with the bug related issue: . On a related note, I wrote the partner to fix the icons.
Flags: needinfo?(hkirschner)

Comment 24

4 years ago
Fixed in

- Go to 
- Log out, log back in, you shouldn't get any errors
- Test that validates
- Test a couple extra hosted apps that you know should validate just in case
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED


4 years ago
Duplicate of this bug: 936564

Comment 26

4 years ago
Verified as fixed :
You need to log in before you can comment on or make changes to this bug.