Looks fine to me, but using another character than / as separator makes it somewhat more readable.. (I usually use |)
s|http://www\.site\.us|http://user:password@www\.site\.us|; This does not generate a redirect, it only rewrites the URL to include password information to be used by Squid when connecting to the site. Supplying such password information only works when Squid is talking directly to the site. It won't work if you have non-Squid parents not using the same trivial extension of http:// URLs. I am not very familiar with SquidGuard. For this to work the password rewrite needs to be just a rewrite of the URL, not a browser redirection. Not many browsers implement this natual extension of http:// URLs and some even uses the same extension for completely different purposes.. Regards Henrik Josh Kuperman wrote: > > Is there something special about how squid as opposed to squidGuard > generates or handles rewriting? > > I am getting odd and unusual as well as varied results trying to do > this using squidGuard instead of squid as the rewriter. Mozilla comes > back with "Redirection limit for this page exceeded. Unable to load > page" while MSIE 6 comes back with its famous and uninformative "the > page you are looking for is unavailable". > > I suspect I just have some sort of squidGuard configuration error. But > before I spend a week of my life on it I would like to know if there > is something unique about redirectors in squid as opposed to squidguard. > > Ages ago in an older squid I was able to supply a user name and passwd > to a site using simply authentication as follows: > > #!/usr/bin/perl > # Redirect from the FAQ > $|=1; > while (<>) { > s/http:\/\/www\.site\.us/http:\/\/user:password\@www\.site\.us/; > } > > No I'm trying to do more or less the same thing with SquidGuard which > lets me insert the roughly equivalent sed command > > s@http://www.site.us@http://user:password\@www.site.us@; > > into a predifined rewrite expression. > > -- > Josh Kuperman > [EMAIL PROTECTED]
