SSL logins not working

[JJoe]

(Oct. 27, 2012 09:15 AM)duebel13 Wrote:  Just after I added the filter "Set-Cookie: Fix cookies when using URL commands (in)" to my configuration, the pages mentioned above are now working as they should:

Don't overlook sidki's warning.

sidki Wrote:Say you log in to that.site.com and your personal data are stored in a cookie, which is restricted to that very host - sometimes for a reason. Now, if you go to this.that.site.com with that filter - as posted - activated, the data cookie would be sent to this host as well.

Filtering https may expose data that should be protected.

ProxRocks Wrote:i advocate that EVERYBODY, new and old, should filter EVERYTHING, ssl or non-ssl...
but i am in the minority in that opinion, i get "flogged" every once in a while for "suggesting" that 'newbies' (not you) FILTER their ssl...

Not to be mean but we win.
Old or new, we want people to educate themselves first. I don't think I've "flogged" anybody but...

ProxRocks Wrote:NOT ONCE has any "flogger" been able to document a case where filtering ssl resulted in any ounce of unintended consequence...

I don't remember anyone telling me that they got hurt. Most people wouldn't be able to figure out why they got burnt. Https may not have been involved in the troubles that I am aware of. I saw my mistake before it bit me, so I guess that experience doesn't count...

For all:

Filtering https may modify data that should not be changed. Half-SSL adds the potential liability of the unencrypted data stream from the Proxomitron to the browser, cookie and routing issues. The data could be account number, password, purchase quantity, etc. Severity of the problem depends on the user and use but, I think, it does exist.

Please be careful.