Bad Request!

[HOOT]

Every once in a while I will get this:

Bad request!

Your browser (or proxy) sent a request that this server could not understand.
If you think this is a server error, please contact the webmaster.
Error 400

208.73.58.131
Mon May 3 10:44:47 2010
Apache

Is it me or the server?

Anyways not a huge deal as I just have to go back to forum.calgarypuck.com and everything is okay. Just curious I guess...

[Yeah_Baby]

In related news I'm off to YouTube to listen to 'Bad Touch'.

[photon]

Weird, I haven't seen anything like that.

[Frank MetaMusil]

I think this has got to be on your PC, not the server. I've never had a bad request return code from Calgarypuck.

You might want to run from a cmd prompt:

ipconfig /flushdns
nbtstat -R
nbtstat -RR

[HOOT]

Originally Posted by photon

Weird, I haven't seen anything like that.

Well fix it! I don't pay all this money to be here for it not to be perfect.

I will try what FM says and see if it works. I've only ever had it happen on one computer I think so many it is trying to grab old stuff from the old server. Just thought I would check to see if I was alone or if it was a problem.

[Azure]

Originally Posted by Frank MetaMusil

nbtstat -R
nbtstat -RR

What does that do?

[Frank MetaMusil]

Originally Posted by Azure

What does that do?

Nbtstat
Nbtstat is designed to help troubleshoot NetBIOS name resolution problems. When a network is functioning normally, NetBIOS over TCP/IP (NetBT) resolves NetBIOS names to IP addresses. It does this through several options for NetBIOS name resolution, including local cache lookup, WINS server query, broadcast, LMHOSTS lookup, Hosts lookup, and DNS server query.