Issue with some mobile websites #2357
Replies: 4 comments 7 replies
-
|
If the mobile version of that site does not show in the logs - then most probably, it means the device was not connecting through the proxy and went directly from the mobile phone to the origin site. Usually this behavior is with QUICK protocol which utilizes UDP connections on ports 80/443 and works completely differently than normal HTTP. The solution is to use your firewall only allowing outbound connections from your proxy to TCP ports 80 (HTTP), 443 (HTTPS) and blocking all other protocols, ports. In addition to that, all outgoing connections from other machines except your proxy should be blocked too. This forces the devices to use proxy for outbound connections and thus all your HTTP(S) connections should go through the proxy and thus be filtered. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your reply. That works when they are inside a corporate network. Any idea on how make this work on a mobile device outside the corporate firewall? It is a mobile device managed via an MDM. We have Chrome policies enabled to force Chrome to use the proxy and also have private DNS set. Google apparently has not made a way in Chrome Management to prevent it from using QUIC since I see no setting for that. Interestingly the DNS server logs show attempts to access a whole host of shein.com domains which were blocked. A closer review of the proxy logs shows an attempt to access shein.com (which is forwarded) but then no more logs for the rest of the traffic. If I am interpreting this correctly, Chrome makes the first attempt to connect to shein.com and then somehow "decides" to do all further communication through QUIC? |
Beta Was this translation helpful? Give feedback.
-
|
I used a desktop computer, navigated to chrome://flags and disable the QUIC protocol completely, restarted chrome and accessed the following URL's: and The log in the proxy showed this: Date and Time Session Policy IP User Status Method Download Upload Domain URL Verdict Module Duration Does that help provide any insight in what might be happening? |
Beta Was this translation helpful? Give feedback.
-
|
I tried with HTTPS decrypting AD integrated (both web safety for linux and web filtering proxy for windows) using Firefox and Edge in an environment where no outgoing QUIC is possible (blocked on the firewall) - and the NSFW term cannot even be searched for - it gets blocked. So if you do not see the QUIC connections to m.shein.com in the logs - it means proxy has no chance to filter it - it also means your browser somehow is able to go out to the internet bypassing the proxy. One way to find it out is to dump all traffic on the machine where your browser runs as explained in https://www.diladele.com/webproxy/docs/faq/proxy/how_to_capture_trafic_on_windows_proxy_netsh/ - and then look for the traffic bypassing the proxy. Also it is a good idea to dump the keys to be able to see the HTTPS contents in the wireshark as explained in https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000HB8gCAG&lang=en_US%E2%80%A9 Finally you can enable dump of sessions in ICAP and manually look at all the contents the proxy had to inspect when going to m.shein.com - see UI / Web Filter / Settings / Network / Dump. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It has come to my attention that on mobile devices, some websites are not being filtered when the mobile version is accessed. For example, if a user visits https://shein.com from a mobile browser is will redirect them to m.shein.com. This mobile version does not show up in the web filter logs and neither does it get filtered. If the user enabled "Desktop Site" on his mobile browser, it will log and be filtered as expected.
Does anyone know what is going on here and how do I fix it?
Beta Was this translation helpful? Give feedback.
All reactions