SSL woes.....
|
Apr. 05, 2007, 02:10 AM
Post: #31
|
|||
|
|||
RE: SSL woes.....
JJoe;
As usual, interesting things for me to try out. I'm busier than a one-legged man in a butt-kicking contest right now, might be a few days before I can report back. Thanks. Oddysey I'm no longer in the rat race - the rats won't have me! |
|||
Apr. 05, 2007, 07:06 PM
Post: #32
|
|||
|
|||
RE: SSL woes.....
JJoe,
First, I tried your tests, and I get the same results you do. Not sure what that proves, except perhaps that I didn't understand your third instruction "If I test "login.yahoo.com/" against test 2's URL Match in the test window, I see "[No Match]".......... when I edit a Header filter, I don't see any kind of test window!!!!!!!!! Now, having gotten a clue from the fact that you keep pointing at the URL Match, I decide to try something. I looked at both my ISP and at Yahoo's secure pages, and I'm damned if several filter aren't firing after all! So, checking the ones that mattered the most to me, I discovered that, 20-20 hindsight being what it is, my whole problem revolves around the URL Match for those allegedly unworking filters. The proof of the pudding is, if I remove the URL match entirely, the filter works, secure page or not. But no matter how I implement a URL Match, secure pages simply get dropped out of the loop. So there's the true underlying problem. The question can be summarized as simply "Why did Proxo suddenly stop filtering secure pages for filters with a URL Match?" And it was suddenly, believe me. I hadn't touched any of those three key filters since last September (or was it October) when I first had a problem, and you gently reminded me to check my IE config itself (to see that it was set up to proxify secure pages). Since that time, I've added several filters, but nothing that replaced (nor even updated) the ones in question. I placed the problem kids at the top of the filter list, I made sure that Multi was turned on, and I even ran a stripped-down subset of filters (shudder!), all just to be sure I hadn't introduced any conflicts. There's no doubt in my unmilitary mind, the URL Match is the source of my problems. The only question now is, do I persue the elegant solution, as intended and implemented by Scott, or do I simply let the filters run on every page I visit, knowing that I'm squandering multiple milleseconds of valuable time? While your help is always invaluable, I think you'd be justified in letting this thing drop in favor of spending time on helping others. Of course, if you should run across a potential solution in the future, I wouldn't be adverse to reading it here on TUOPF! Thanks JJoe, you're still Aces in my book! Oddysey I'm no longer in the rat race - the rats won't have me! |
|||
Apr. 05, 2007, 09:30 PM
Post: #33
|
|||
|
|||
RE: SSL woes.....
Oddysey Wrote:First, I tried your tests, and I get the same results you do. Not sure what that proves,It proves: https://foo.com/ is not matched by a URL Match of "foo.com/". https://foo.com/ is matched by a URL Match of "foo.com:". The Proxomitron sees or treats https://foo.com/ as https://foo.com:443/ URL Matches must accommodate this behaviour. Oddysey Wrote:when I edit a Header filter, I don't see any kind of test window!!!!!!!!!Right-click on the URL Match field and choose "Test matching". Oddysey Wrote:the URL Match is the source of my problems.If you want to match https://login.yahoo.com/config/login_verify2?&.src=ym , you could use a URL Match of "login.yahoo.com" or "login.yahoo.com:". sidki's Yahoo: Auto Login filter uses Code: (^$KEYCHK(^C^A))$TYPE(htm)([^.]+.yahoo.com(:[0-9]+|)/config/(login(_verify2|)|mail)\?(\&+.|(^?))|mail.yahoo.com/) Oddysey Wrote:I made sure that Multi was turned onMulti allows filters to match the output of the multi enabled filter. Oddysey Wrote:I think you'd be justified in letting this thing drop in favor of spending time on helping others.This is a public forum. I hope helping you will help others. |
|||
Apr. 08, 2007, 03:43 PM
Post: #34
|
|||
|
|||
RE: SSL woes.....
JJoe;
You Wrote:Yes, but I was thinking more along the lines of 'this doesn't solve my URL matching dilemma'. Wait, more to follow, read on.......Oddysey Wrote:First, I tried your tests, and I get the same results you do. Not sure what that proves,It proves: You Wrote:Ah, the virtues of reading the documentation. It's there, under the Header Filter Editor section, but it's not intuitively obvious like the button for the test window in the Web Filters that shows you what happens with actual text. And of course, a quick check shows that the same method applies for testing URL Matches in the Web Filters, too.Oddysey Wrote:when I edit a Header filter, I don't see any kind of test window!!!!!!!!!Right-click on the URL Match field and choose "Test matching". You Wrote:As often as not, I find that sidki's filters sometimes are too exacting. . Watch this:Oddysey Wrote:the URL Match is the source of my problems.If you want to match https://login.yahoo.com/config/login_verify2?&.src=ym, Code: URL Match = [^/]++login.yahoo.com\w/ You Wrote:That's true. What I was doing was making sure that I didn't have one filter stepping on another. Turns out I did, but that was a side effect, and easily cured, once I was on to the URL Match thing.Oddysey Wrote:I made sure that Multi was turned onMulti allows filters to match the output of the multi enabled filter. You Wrote:Well hey, far be it from be to hold a good man down!!!Oddysey Wrote:I think you'd be justified in letting this thing drop in favor of spending time on helping others.This is a public forum. But I think the \w will solve the problem. Oddysey I'm no longer in the rat race - the rats won't have me! |
|||
« Next Oldest | Next Newest »
|