(Nov. 12, 2009 02:25 AM)ramsy Wrote:  

Quote:HTTP/1.0?
Can you enable 1.1?

How is this accomplished.

(Nov. 12, 2009 05:41 AM)JJoe Wrote:  Re: Can you enable 1.1?

(Nov. 12, 2009 05:41 AM)JJoe Wrote:  Is it always Firefox>Proxomitron>Privoxy>Tor>Bank

(Nov. 12, 2009 05:26 PM)ramsy Wrote:  Is there an issue with my Firefox Help/About version info. below:

"Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3"

---

(Nov. 12, 2009 05:26 PM)ramsy Wrote:  

(Nov. 12, 2009 05:41 AM)JJoe Wrote:  Re: Can you enable 1.1?

No such option exists in either Firefox or IE Settings

(Nov. 12, 2009 10:17 PM)JJoe Wrote:  

Code:

([^/]++.|)chase.com: $SET(0=i_ua:0.)

to $LST(IncludeExclude-U) or equiv.

(Nov. 12, 2009 10:17 PM)JJoe Wrote:  Looks like Firefox has it enabled by default...

(Nov. 13, 2009 09:16 AM)ramsy Wrote:  If there's no other advantage to the IncludeExclude-U code vs User-Agents Line: 45, perhaps I should be satisfied with my host file entry for "doubleclick.net" and just add [^/]++chase.com to Proxo's "bypass list.txt"?

(Nov. 13, 2009 09:16 AM)ramsy Wrote:  Since current logs reference HTTP 1.1, I believe the earlier HTTP 1.0 was a function of Vidalia/Tor/Privoxy, not currently running.

http://www.privoxy.org/user-manual/actions-file.html Wrote:8.5.13. downgrade-http-version

Typical use:

Work around (very rare) problems with HTTP/1.1
Effect:

Downgrades HTTP/1.1 client requests and server replies to HTTP/1.0.
Type:

Boolean.
Parameter:

N/A
Notes:

This is a left-over from the time when Privoxy didn't support important HTTP/1.1 features well. It is left here for the unlikely case that you experience HTTP/1.1 related problems with some server out there. Not all HTTP/1.1 features and requirements are supported yet, so there is a chance you might need this action.
Example usage (section):

{+downgrade-http-version}
problem-host.example.com

(Nov. 13, 2009 09:41 AM)ProxRocks Wrote:  i try NEVER to bypass Proxo...
here is my current IncExc-U entry for Chase:

Code:

# Chase
[^/]++.chase.com[:/]
    $SET(0=so.half-ssl-mod.rev_link.a_tpi.a_code.a_jslink.i_script:0.i_spoof:0.)
    $SET(1=cookie_b:0.cookie_s:1.)
    $SET(sAdKey=.grayTextSm.)

here is the "modified" half-ssl filter:

Code:

In = TRUE
Out = FALSE
Key = "Location: 4b Half-SSL     9.04.10 (cch!) [jjoe] (d.2) (In) [add]"
URL = "$TST(keyword=(*.half-ssl-mod.)*.i_ssl_h:[12].*)"
Match = "https://(\1\?$SET(#=?)(\#\=https%3a%2f%2f$SET(#==http%3A%2F%2Fhttps-px-.))+\#|\1)"
Replace = "http://https-px-.\1\@"

(Nov. 14, 2009 07:05 PM)ProxRocks Wrote:  it works for me in Firefox, BUT ..via Comodo firewall ..i REFUSE to allow Firefox ANYTHING outside of ..UDP 8080... ANY web browser that feels they need "more" than that should NOT be trusted, in my opinion...

(Mar. 12, 2010 04:57 PM)ProxRocks Wrote:  it's been "ages" since i've tried the 'newer' Comodo (i'm still on, and prefer, v2.4.18.184)...

(Mar. 12, 2010 05:49 PM)ProxRocks Wrote:  i shouldn't have to jump through so many hoops to set up port-specific firewall rules...