> Hi,
>
> I was running uWSGI directly on the internet facing website in HTTP+HTTPS
> mode. Recently the following errors started to pop up - according to the
> logs the server sent the page, but Chrome reported network failure. This
> is
> probably not Chrome related, but in Chrome the problem was most
> repeatable:
> some pages did not open every time.
>
> I inspected the problem with wget and looks like it is some sort of TLS
> issue. You can find the diagnostics output below.
>
> I decided not to investigate further, but simply added Nginx at the front
> to handle HTTP/HTTPS and use WSGI to talk to uWSGI, as recommended on this
> mailing list earlier. Problem solved.
>
> Just to let you know if somebody else uses uWSGI for raw HTTPS traffic.
>
> --
> Mikko Ohtamaa
> http://opensourcehacker.com
> http://twitter.com/moo9000
>
>
> [/tmp]% wget -S --no-check-certificate "
> https://libertymusicstore.net/store/sol-music/embed/";
> --2014-10-24 09:21:38--
> https://libertymusicstore.net/store/sol-music/embed/
> Resolving libertymusicstore.net (libertymusicstore.net)... 78.47.124.242
> Connecting to libertymusicstore.net
> (libertymusicstore.net)|78.47.124.242|:443...
> connected.
> WARNING: The certificate of ‘libertymusicstore.net’ is not trusted.
> WARNING: The certificate of ‘libertymusicstore.net’ hasn't got a known
> issuer.
> HTTP request sent, awaiting response...
>   HTTP/1.1 200 OK
>   Content-Type: text/javascript
> Length: unspecified [text/javascript]
> Saving to: ‘index.html’
>
>     [
> <=>
> ] 1,213       --.-K/s   in 0s
>
> 2014-10-24 09:21:39 (23.6 MB/s) - Read error at byte 1213 (The TLS
> connection was non-properly terminated.).Retrying.
>
> --2014-10-24 09:21:40--  (try: 2)
> https://libertymusicstore.net/store/sol-music/embed/
> Connecting to libertymusicstore.net
> (libertymusicstore.net)|78.47.124.242|:443...
> connected.
> WARNING: The certificate of ‘libertymusicstore.net’ is not trusted.
> WARNING: The certificate of ‘libertymusicstore.net’ hasn't got a known
> issuer.
> HTTP request sent, awaiting response...
>   HTTP/1.1 200 OK
>   Content-Type: text/javascript
> Length: unspecified [text/javascript]
> Saving to: ‘index.html’
>
>     [
> <=>
> ] 0           --.-K/s   in 0s
>
>

If you are on Yosemite there are reports all over the place about this
error (not uWSGI related), unfortunately i still did not have the time to
bring up a yosemite machine (maybe this weekend)

If this happens out of osx yosemite systems, i need some more detail, like
the openssl/gnutls library used.

Thanks a lot


-- 
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to