Posted: Mon Apr 07, 2014 17:18 Post subject: Privoxy (HTTPS versus HTTP) and router logon screen issue
I enabled privoxy on my TP-LINK WDR4900 (build 23838 - transparant mode disabled):
If I do a https request from a windows 8.1 IE11 internal machine (192.168.1.119) to my internal server: https://mywebserver.mydomain.nl (192.168.1.5) I have no problem.
If I do the same request but as http I do get the router logon window of my TP-LINK DD-WRT (gateway 192.168.1.254) router:
http://mywebserver.mydomain.nl
Why? Can it be fixed?
note 1: If I ping mywebserver.mydomain.nl it wil give the correct internal IP of mywebserver (192.168.1.5) and I have my own Windows Server 2012 R2 Domain (Active Directory, DNS, DHCP, Exchange etc.) and Group Policy to activated Privoxy on all browsers and computers and users (computers are all joined in the domain mydomain).
Note 2: If I disable Privoxy everything is working fine....
Note 3: Except this issue privoxy is great (IE11 & Chrome), the same issue occurs with Chrome...
Posted: Tue Apr 15, 2014 19:44 Post subject: Re: Privoxy (HTTPS versus HTTP) and router logon screen issu
nlapplegate wrote:
I enabled privoxy on my TP-LINK WDR4900 (build 23838 - transparant mode disabled):
If I do a https request from a windows 8.1 IE11 internal machine (192.168.1.119) to my internal server: https://mywebserver.mydomain.nl (192.168.1.5) I have no problem.
If I do the same request but as http I do get the router logon window of my TP-LINK DD-WRT (gateway 192.168.1.254) router:
http://mywebserver.mydomain.nl
Why? Can it be fixed?
note 1: If I ping mywebserver.mydomain.nl it wil give the correct internal IP of mywebserver (192.168.1.5) and I have my own Windows Server 2012 R2 Domain (Active Directory, DNS, DHCP, Exchange etc.) and Group Policy to activated Privoxy on all browsers and computers and users (computers are all joined in the domain mydomain).
Note 2: If I disable Privoxy everything is working fine....
Note 3: Except this issue privoxy is great (IE11 & Chrome), the same issue occurs with Chrome...
Not quite sure what you are talking about, but seems your proxy is anonymizing your requests. That's why your webface re-asks auth. In the case of HTTPS, squid-like proxies simply pass the traffic through doing nothing, until some https or dynamic content addon is plugged in the chain.