firewalls "removing bogus header"

[Karl Seguin]

Some of our users behind firewalls (watchguard in particular) are reporting
that they can't access our site. This is the type of error they are
getting:

02/06/04 07:27 http-proxy[13348]: [200.8.8.31:2990 204.225.90.54:80]
removing bogus HTTP header "GET
/Disclaimer.aspx?Mode=0&Page=1&vs=1&rlt=&cp=&pt=32&mp=0-0-0&mrt=-1-0-0&Beds=
3-0&Baths=2-0&f=&ft=all&o=A&

The site in question is www.mls.ca, clicking on a province, selecting
checkboxes from the left, clicking "Seach" and then doing an advanced search
from the form that comes up.

We are obviously sending headers that don't conform to the RFC, but are at a
loss to identify the specific problem. If anyone could shed some light onto
this, it'd be greatly appreciated.

Karl

 

[John Saunders]

Some of our users behind firewalls (watchguard in particular) are reporting
that they can't access our site. This is the type of error they are
getting:

02/06/04 07:27 http-proxy[13348]: [200.8.8.31:2990 204.225.90.54:80]
removing bogus HTTP header "GET
/Disclaimer.aspx?Mode=0&Page=1&vs=1&rlt=&cp=&pt=32&mp=0-0-0&mrt=-1-0-0&Beds=
3-0&Baths=2-0&f=&ft=all&o=A&

The site in question is www.mls.ca, clicking on a province, selecting
checkboxes from the left, clicking "Seach" and then doing an advanced search
from the form that comes up.

We are obviously sending headers that don't conform to the RFC, but are at a
loss to identify the specific problem. If anyone could shed some light onto
this, it'd be greatly appreciated.

Only a wild guess: why does your query string end in an ampersand (&)?

 

[Karl Seguin]

John,
I don't think it does, I think their firewall log stripped part of it out
for display and that was just copied & pasted. Will definetly set up a test
to see if that's the specific problem though.

Karl

Some of our users behind firewalls (watchguard in particular) are reporting
that they can't access our site. This is the type of error they are
getting:

02/06/04 07:27 http-proxy[13348]: [200.8.8.31:2990 204.225.90.54:80]
removing bogus HTTP header "GET

/Disclaimer.aspx?Mode=0&Page=1&vs=1&rlt=&cp=&pt=32&mp=0-0-0&mrt=-1-0-0&Beds=

3-0&Baths=2-0&f=&ft=all&o=A&

The site in question is www.mls.ca, clicking on a province, selecting
checkboxes from the left, clicking "Seach" and then doing an advanced search
from the form that comes up.

We are obviously sending headers that don't conform to the RFC, but are

at

a
loss to identify the specific problem. If anyone could shed some light onto
this, it'd be greatly appreciated.

Only a wild guess: why does your query string end in an ampersand (&)?

 

[John Saunders]

John,
I don't think it does, I think their firewall log stripped part of it out
for display and that was just copied & pasted. Will definetly set up a test
to see if that's the specific problem though.

Karl

Some of our users behind firewalls (watchguard in particular) are reporting
that they can't access our site. This is the type of error they are
getting:

02/06/04 07:27 http-proxy[13348]: [200.8.8.31:2990 204.225.90.54:80]
removing bogus HTTP header "GET

/Disclaimer.aspx?Mode=0&Page=1&vs=1&rlt=&cp=&pt=32&mp=0-0-0&mrt=-1-0-0&Beds= are

at light
onto

Only a wild guess: why does your query string end in an ampersand (&)?

Also, Karl, could we see the entire header before it's stripped?

 

[George Ter-Saakov]

As i understand you are using GET.
I am affraid that in this case URL gets too long.

Change method to POST and try.

George.