cancel
Showing results for 
Search instead for 
Did you mean: 
btlyric
Level 12

Force HTTP/1.0 for specific destionation?

Jump to solution

Is it possible to force HTTP/1.0 for a specific destionation?

Internet Explorer 8, HTTP/1.1 forced via GPO, connection via WCCP, destination site (http://www.binghamton.edu) sends an immediate RST when it sees GET / HTTP/1.1 (verified via tcpdump).

If I configure direct proxy, IE works even if Internet Options -> Advanced -> Use HTTP 1.1 for proxy connections is selected.

0 Kudos
1 Solution

Accepted Solutions
eelsasser
Level 15

Re: Force HTTP/1.0 for specific destionation?

Jump to solution

Make a rule with whatever criteria you want it to match on, destination, site, client.ip, etc. (Request Cycle)

Create an event that sets  the property Request.ProtocolAndVersion:

Events:

Set Request.ProtocolAndVersion = "HTTP/1.0"

0 Kudos
4 Replies
eelsasser
Level 15

Re: Force HTTP/1.0 for specific destionation?

Jump to solution

Make a rule with whatever criteria you want it to match on, destination, site, client.ip, etc. (Request Cycle)

Create an event that sets  the property Request.ProtocolAndVersion:

Events:

Set Request.ProtocolAndVersion = "HTTP/1.0"

0 Kudos
btlyric
Level 12

Re: Force HTTP/1.0 for specific destionation?

Jump to solution

Must be something else going on. That alone doesn't make the site work. I have a workaround for the customer so will revisit.

Thanks!

0 Kudos
McAfee Employee

Re: Force HTTP/1.0 for specific destionation?

Jump to solution

You also might want to try the proxy control event and check the options in there.

Specifically, one of the 1st 3 options:

override chunk encoding

content-length header

persistent connection handling.

thanks,

Michael

0 Kudos
btlyric
Level 12

Re: Force HTTP/1.0 for specific destionation?

Jump to solution

Seems that there was something related to browser identification. I didn't directly work on the final solution, but as I understand it, if the user-agent was IE, something (perhaps Accept-Encoding) would get munged, but only in WCCP mode. Implementing a user-agent rewrite at MWG served as a usable workaround.

0 Kudos