Reply To: Mobile app "unable to connect" through SSL reverse proxy (Apache)

[ipilcher]

I’m pretty much convinced that the proxy isn’t adding the slash. I managed to use wireshark to decrypt the SSL traffic between the app and the proxy, and I can see the app sending the request with the extra slash:

GET /js/?pw=f7a9f061ae223e7ed166a73abe2abd8a HTTP/1.1
Host: www.penurio.us:32697
Connection: keep-alive
Accept: application/json, text/javascript, */*; q=0.01
User-Agent: Mozilla/5.0 (Linux; Android 4.4.4; A0001 Build/KTU84Q) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/33.0.0.0 Mobile Safari/537.36
Accept-Encoding: gzip,deflate
Accept-Language: en-US
X-Requested-With: com.albahra.sprinklers

HTTP/1.1 200 OK
Date: Thu, 27 Aug 2015 22:11:52 GMT
Content-Type: application/json
Access-Control-Allow-Origin: *
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Connection: close
Transfer-Encoding: chunked

d
{"result":32}
0

I also connected to the phone with Chrome, as you suggested, and the Console tab shows a bunch of errors like:

Failed to load resource: net::ERR_FAILED https://www.penurio.us:32697/js/?pw=f7a9f061ae223e7ed166a73abe2abd8a

(With the extra slash.)

On the network tab, however, the URLs don’t have the slash.

And ….. son of a B, it works on a different phone! It looks like the phone OS is munging the URLs for some reason.