Re:Nike.com's robots.txt
by cookiengineer on Friday February 11, 2022 @12:04PM
(#30303817)
Did you try to breakout using pwnat to get a public port? In enterprise grade environments it usually works :D
I think I'd also try to run a UDP tunnel or try to use an amplification redirect on a UDP relaying proxy to get an open port that you can send requests through. Sometimes public DNS resolvers can help to punch a hole through the NAT because their IPs are allowlisted to unbreak secure browsing modes.
> re: stealth
I forked webkit into retrokit [1] these days and am gradually removing all APIs that could be abused for tracking purposes ... with the idea to create a minimalistic webview that is embeddable in a browser and still is able to parse/lex/render modern HTML5 and CSS4.
This way I can later bundle nodejs with the retrokit webview that just displays the Browser UI that's served locally.
Re:Nike.com's robots.txt
by carapace on Saturday February 12, 2022 @11:23AM
(#30313923)
I don't think it's a network issue (we're at home) because all the other browsers work. This version of FF is just weird about HTTP2/SPDY. I don't want to shave this yak.
I think I'd also try to run a UDP tunnel or try to use an amplification redirect on a UDP relaying proxy to get an open port that you can send requests through. Sometimes public DNS resolvers can help to punch a hole through the NAT because their IPs are allowlisted to unbreak secure browsing modes.
> re: stealth
I forked webkit into retrokit [1] these days and am gradually removing all APIs that could be abused for tracking purposes ... with the idea to create a minimalistic webview that is embeddable in a browser and still is able to parse/lex/render modern HTML5 and CSS4.
This way I can later bundle nodejs with the retrokit webview that just displays the Browser UI that's served locally.
[1] https://github.com/tholian-network/retrokit