: Http2 and Alternate-Protocol, ngnix open src web server config My goal is to know if my android app and my browser are talking to my web server on http2. Using open source nginx stable 1.12

@Si4351233

Posted in: #Http #Https

My goal is to know if my android app and my browser are talking to my web server on http2. Using open source nginx stable 1.12 on linux.

Looking at the network or other tools of firefix (version 54) or chrome (version 59) can we tell that ?

Response Headers I get on hitting sub domain (like a.my.com/):
Date: Thu, 13 Jul 2017 11:02:06 GMT
Last-Modified: Wed, 12 Apr 2017 14:46:01 GMT
Connection: keep-alive
Etag: "58ee3da9-264"
Server: WebServer
Strict-Transport-Security: max-age=63072000
x-frame-options: DENY
X-Content-Type-Options: nosniff
Cache-Control: no-cache
Alternate-Protocol: 443:npn-spdy/3


But when I hit a page (https://a.my.com/b/c/) the last header is not returned. My app hits a page like that.
Response Headers:

Date: Thu, 13 Jul 2017 11:11:13 GMT
Content-Type: application/json
Content-Length: 235
Connection: keep-alive
Access-Control-Allow-Headers: origin, content-type, accept, authorization
access-control-allow-credentials: true
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS, HEAD
Vary: Accept-Encoding
Content-Encoding: gzip
Server: WebServer
x-frame-options: SAMEORIGIN


Does the client browser hit the base URL to get the protocol anyway without logging it? (I opened a reopened my browser and tried in a private window, to hit the page first, still did not see the Protocol info).

Just curious if its a config thing/ if it matters or trust the clients to use the best protocol without changing anything on the server or android app code?

Vote Up Vote Down

Login to post a comment!