HTTP 400 Bad Request

The web site didn't help me.

I have a similar problem.

We are trying to access http://xxx.xxx.xxx.xxx printer monitoring pages.
We have a few IE 7.0 that can access it and several that can not. Firefox
works on all links in question.

The IE 7.0 are a similar build (rolled out to departments) and we can not
find what is different about them. Setting everything back to default
doesn't help, adding site to the trusted sites doesn't help. Proxy settings
and user rights are similar.

Anybody have any thoughts at all, very aggravating issue.

Thanks

"Kaja" wrote:

>
> hi, see if this helps
> http://www.checkupdown.com/status/E400.html
> "Carpie" wrote:
>
> > I am receiving the above message constantly and consistently. I believe it
> > is a result of installing Verizon's Vcast Music Manager software as it has
> > begun to occur after that. Now when I try to do certain things on certain
> > sites (ie login to myspace, delete a message from yahoo, etc), the message
> > pops up. It is definitely a client side issue and not server side. I have
> > downloaded and installed IE7 SP2 but it did not help. In fact I had to
> > download Firefox just to get to these sites including this one to post. Any
> > ideas would be greatly appreciated.
 >> Stay informed about: HTTP 400 Bad Request 

Not sure this will be helpful but:

Failed:

- Http: Response, HTTP/1.0, Status Code = 400
- Response:
ProtocolVersion: HTTP/1.0
StatusCode: 400, Bad request
Reason: Bad Request
ContentLength: 15
ContentType: text/html
Age: 202
X-Cache: HIT from Proxy
Proxy-Connection: keep-alive
HeaderEnd: CRLF
- payload: HttpContentType = text/html
HtmlElement: 400 Bad Request


Success:

- Http: Response, HTTP/1.0, Status Code = 200
- Response:
ProtocolVersion: HTTP/1.0
StatusCode: 200, Ok
Reason: OK
ContentType: text/html
ContentLength: 138
X-Cache: MISS from Proxy
Proxy-Connection: keep-alive
HeaderEnd: CRLF
- payload: HttpContentType = text/html
HtmlElement: GIF89a=

The printer websites are not setup to cache on the proxy.
 >> Stay informed about: HTTP 400 Bad Request 

"Bob" <Bob.DeleteThis@discussions.microsoft.com> wrote in message
news:6B3CC96C-FB10-4369-9B73-3DFFA3588453@microsoft.com...
> Not sure this will be helpful but:
>
> Failed:
>
> - Http: Response, HTTP/1.0, Status Code = 400


Try using HTTP/1.1 instead?


> - Response:
> ProtocolVersion: HTTP/1.0
> StatusCode: 400, Bad request
> Reason: Bad Request
> ContentLength: 15
> ContentType: text/html
> Age: 202
> X-Cache: HIT from Proxy
> Proxy-Connection: keep-alive


Can you connect to the site by bypassing your proxy?
Some sites seem to dislike conducting exchanges through a proxy.


> HeaderEnd: CRLF
> - payload: HttpContentType = text/html
> HtmlElement: 400 Bad Request
>
>
> Success:
>
> - Http: Response, HTTP/1.0, Status Code = 200
> - Response:
> ProtocolVersion: HTTP/1.0
> StatusCode: 200, Ok
> Reason: OK
> ContentType: text/html
> ContentLength: 138
> X-Cache: MISS from Proxy
> Proxy-Connection: keep-alive
> HeaderEnd: CRLF
> - payload: HttpContentType = text/html
> HtmlElement: GIF89a=
>
> The printer websites are not setup to cache on the proxy.
>
 >> Stay informed about: HTTP 400 Bad Request 

I get the same results either way...



"Robert Aldwinckle" wrote:

> "Bob" <Bob.TakeThisOut@discussions.microsoft.com> wrote in message
> news:6B3CC96C-FB10-4369-9B73-3DFFA3588453@microsoft.com...
> > Not sure this will be helpful but:
> >
> > Failed:
> >
> > - Http: Response, HTTP/1.0, Status Code = 400
>
>
> Try using HTTP/1.1 instead?
>
>
> > - Response:
> > ProtocolVersion: HTTP/1.0
> > StatusCode: 400, Bad request
> > Reason: Bad Request
> > ContentLength: 15
> > ContentType: text/html
> > Age: 202
> > X-Cache: HIT from Proxy
> > Proxy-Connection: keep-alive
>
>
> Can you connect to the site by bypassing your proxy?
> Some sites seem to dislike conducting exchanges through a proxy.
>
>
> > HeaderEnd: CRLF
> > - payload: HttpContentType = text/html
> > HtmlElement: 400 Bad Request
> >
> >
> > Success:
> >
> > - Http: Response, HTTP/1.0, Status Code = 200
> > - Response:
> > ProtocolVersion: HTTP/1.0
> > StatusCode: 200, Ok
> > Reason: OK
> > ContentType: text/html
> > ContentLength: 138
> > X-Cache: MISS from Proxy
> > Proxy-Connection: keep-alive
> > HeaderEnd: CRLF
> > - payload: HttpContentType = text/html
> > HtmlElement: GIF89a=
> >
> > The printer websites are not setup to cache on the proxy.
> >
>
>
>
 >> Stay informed about: HTTP 400 Bad Request 

Fix (for us anyway):

Delete the entries under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet
Settings\Accepted Documents

Except for default.

You can try the following first, although copying it from a pc that worked
did not work for us, we needed to delete everything but the default as
mentioned above:

1. On a computer that is working navigate to this registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet
Settings\Accepted Documents

2. Export “Accepted Documents” and save it as good_ Accepted Documents.reg

3. Then on the problem computer navigate to the same registry as step 1 and
backup that key and name it bad_ Accepted Documents.reg

4. Once the key is backed up delete Accepted Documents on the problem
computer and then double click on good_ Accepted Documents.reg
to import the key

5. Reboot the problem computer after step 4 is done and test accessing the
printer web interface with Internet Explorer.

Further info:

It may be an issue between .net 2.x and .net 3.x, the one that was working
had .net 2.x and the ones that did not were running .net 3.x








"Bob" wrote:

> I get the same results either way...
>
>
>
> "Robert Aldwinckle" wrote:
>
> > "Bob" <Bob.RemoveThis@discussions.microsoft.com> wrote in message
> > news:6B3CC96C-FB10-4369-9B73-3DFFA3588453@microsoft.com...
> > > Not sure this will be helpful but:
> > >
> > > Failed:
> > >
> > > - Http: Response, HTTP/1.0, Status Code = 400
> >
> >
> > Try using HTTP/1.1 instead?
> >
> >
> > > - Response:
> > > ProtocolVersion: HTTP/1.0
> > > StatusCode: 400, Bad request
> > > Reason: Bad Request
> > > ContentLength: 15
> > > ContentType: text/html
> > > Age: 202
> > > X-Cache: HIT from Proxy
> > > Proxy-Connection: keep-alive
> >
> >
> > Can you connect to the site by bypassing your proxy?
> > Some sites seem to dislike conducting exchanges through a proxy.
> >
> >
> > > HeaderEnd: CRLF
> > > - payload: HttpContentType = text/html
> > > HtmlElement: 400 Bad Request
> > >
> > >
> > > Success:
> > >
> > > - Http: Response, HTTP/1.0, Status Code = 200
> > > - Response:
> > > ProtocolVersion: HTTP/1.0
> > > StatusCode: 200, Ok
> > > Reason: OK
> > > ContentType: text/html
> > > ContentLength: 138
> > > X-Cache: MISS from Proxy
> > > Proxy-Connection: keep-alive
> > > HeaderEnd: CRLF
> > > - payload: HttpContentType = text/html
> > > HtmlElement: GIF89a=
> > >
> > > The printer websites are not setup to cache on the proxy.
> > >
> >
> >
> >
 >> Stay informed about: HTTP 400 Bad Request 

hi carpie, i have the exact same problem now. i am running vista home basic,
with norton antivirus 2008 and vcast music manager. i have tried all sorts
of different configurations of the internet explorer through the internet
options, windows firewall, etc. did you get a final resolve for this issue
or are you still running firefox?

"Carpie" wrote:

> I am receiving the above message constantly and consistently. I believe it
> is a result of installing Verizon's Vcast Music Manager software as it has
> begun to occur after that. Now when I try to do certain things on certain
> sites (ie login to myspace, delete a message from yahoo, etc), the message
> pops up. It is definitely a client side issue and not server side. I have
> downloaded and installed IE7 SP2 but it did not help. In fact I had to
> download Firefox just to get to these sites including this one to post. Any
> ideas would be greatly appreciated.
 >> Stay informed about: HTTP 400 Bad Request 

You're not running IE6 either.

Those with IE7-specific questions or comments are asked to post to and seek
support in this newsgroup: microsoft.public.internetexplorer.general

On the web:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=...rosoft.

In your newsreader:
news://msnews.microsoft.com/microsoft.public.internetexplorer.general
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/


imack606 wrote:
> hi carpie, i have the exact same problem now. i am running vista home
> basic, with norton antivirus 2008 and vcast music manager. i have tried
> all sorts of different configurations of the internet explorer through the
> internet options, windows firewall, etc. did you get a final resolve for
> this issue or are you still running firefox?
<snip>
 >> Stay informed about: HTTP 400 Bad Request 

thanks, i have reposted as you directed.

"PA Bear [MS MVP]" wrote:

> You're not running IE6 either.
>
> Those with IE7-specific questions or comments are asked to post to and seek
> support in this newsgroup: microsoft.public.internetexplorer.general
>
> On the web:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=...rosoft.
>
> In your newsreader:
> news://msnews.microsoft.com/microsoft.public.internetexplorer.general
> --
> ~Robear Dyer (PA Bear)
> MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
> AumHa VSOP & Admin http://aumha.net
> DTS-L http://dts-l.net/
>
>
> imack606 wrote:
> > hi carpie, i have the exact same problem now. i am running vista home
> > basic, with norton antivirus 2008 and vcast music manager. i have tried
> > all sorts of different configurations of the internet explorer through the
> > internet options, windows firewall, etc. did you get a final resolve for
> > this issue or are you still running firefox?
> <snip>
>
>
 >> Stay informed about: HTTP 400 Bad Request