Arch Linux

marove

Member

Registered: 2015-12-17

Posts: 9

http request returns strange binary data

Hello together,

I've just moved from a Debian to an Arch server but running in some problems. I'm running web applications on an nginx with the following config:

vhost: https://gist.github.com/anonymous/46dec … cbdd439ccd
nginx.conf: https://gist.github.com/anonymous/54f6d … b0ccbbe3f7

If I now try to enter http://2wickl.de in the browser (or CURL) I'll just get back strange binary data (%).
Only if I directly enter https://2wickl.de I'll get back the correct output. Even when I'm trying something like http://aasdflaksdflalsfdj.2wickl.de it does not work. If I try https://aasdflaksdflalsfdj.2wickl.de it works just as is should. I think, the nginx does not really get the chance to redirect or deliver the default site on port 80. Can anybody give me some hints, where I can have a look or did something wrong?

netstat -a -p -n|grep LISTEN delivers:
https://gist.github.com/anonymous/54d2d … 0111f1135d

Thanks already for your help.

Regards
marove

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,523

Website

Re: http request returns strange binary data

I don't get any strange binary data back.  I get nothing from curl.  From telnet I see the connection is immediately closed in response to a GET request:

$ telnet 2wickl.de 80
Trying 138.201.66.162...
Connected to 2wickl.de.
Escape character is '^]'.
GET /index.html
Connection closed by foreign host.

I can send a successful GET request with openssl on port 443.

---

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

marove

Member

Registered: 2015-12-17

Posts: 9

Re: http request returns strange binary data

Hello Trilby,

thanks for the fast reply. Any suggestions what I can try? This is very strangy. Why does 443 work but not 80.

Regards
marove

marove

Member

Registered: 2015-12-17

Posts: 9

Re: http request returns strange binary data

After some further investigation I found the problem:

One of my server-configurations had http2 enabled for http port 80

    server {
        listen 80 http2;
        listen [::]:80 http2;
    }

After changing to

    server {
        listen 80;
        listen [::]:80;
    }

Everything works fine again. It is always a good advise to deactivate all server-settings and turn on every server one by one.