On 3/09/2015 7:47 a.m., Oliver Webb wrote:
> Currently the rewriter is only being sent ":443" and at no
> point gets sent the URL starting https.
> Any ideas why this might be happening?
The "bump" part is not happening. You will have to look into why not.
Though be aware that ssl-bump is an MIT
When a browser requests https://www.example.com/index.html, Squid with ssl-bump
sends two requests to the URL rewriter:
1. CONNECT www.example.com:443
2. GET https://www.example.com/index.html
The URL rewriter must _not_ block the first and send an alternative URL for the
second.
Caveat: thi
On 2/09/2015 12:59 p.m., Oliver Webb wrote:
> Hopefully quite a simple one (to ask anyway!):
> In Squid 3.5.7 *with working Peek and Splice* how can I give my
> url_rewrite_program access to the decrypted URL?
> eg. https://example.com/malware-that-the-url-rewriter-will-block.exe.pdf
You nee
Hopefully quite a simple one (to ask anyway!):
In Squid 3.5.7 *with working Peek and Splice* how can I give my
url_rewrite_program access to the decrypted URL?
eg. https://example.com/malware-that-the-url-rewriter-will-block.exe.pdf
Many Thanks,
Oliver
