If you remove the user-agent from the request headers or use some user-agent that google doesn't recognize, it sends some weird mobile page to the browser, which Proxydomo fails to filter. If I enable the Web Filter Debug in the Log window and load the page, Proxydomo just displays some binary (gzipped ?) output. Could you please look into this issue?
https://github.com/amate/Proxydomo/issues/new
Request:
Request sent to website
GET /search?hl=en&nfpr=1&prmd=u&q=a HTTP/1.1
Accept: text/html, application/xhtml+xml, image/jxr, /
Accept-Language: en-GB,en-US,en,de-DE,ru-RU
Accept-Encoding: gzip, deflate
User-Agent: AdsBot-Google
Host: www.google.de
DNT: 1
Connection: Keep-Alive
Response:
Response sent to browser
HTTP/1.1 200 OK
Content-Type: application/xhtml+xml; charset=ISO-8859-1
Date: Sat, 30 Nov 2019 23:41:58 GMT
Content-Encoding: gzip
Transfer-Encoding: chunked
Access-Control-Allow-Origin: *
If you remove the user-agent from the request headers or use some user-agent that google doesn't recognize, it sends some weird mobile page to the browser, which Proxydomo fails to filter. If I enable the Web Filter Debug in the Log window and load the page, Proxydomo just displays some binary (gzipped ?) output. Could you please look into this issue?
https://github.com/amate/Proxydomo/issues/new
Request:
Request sent to website
GET /search?hl=en&nfpr=1&prmd=u&q=a HTTP/1.1
Accept: text/html, application/xhtml+xml, image/jxr, /
Accept-Language: en-GB,en-US,en,de-DE,ru-RU
Accept-Encoding: gzip, deflate
User-Agent: AdsBot-Google
Host: www.google.de
DNT: 1
Connection: Keep-Alive
Response:
Response sent to browser
HTTP/1.1 200 OK
Content-Type: application/xhtml+xml; charset=ISO-8859-1
Date: Sat, 30 Nov 2019 23:41:58 GMT
Content-Encoding: gzip
Transfer-Encoding: chunked
Access-Control-Allow-Origin: *