Firefox flips out with "400 bad request"

[FLBentRider]

What the heck are y'all taking about?

----
Don't matter.  Just get CHROME.  It rocks.
AND --- The javascript engine is WICKED FAST in CHROME.
(yes, I've timed it).
Awrighten.

Chrome is not fit for a corporate environment. For consumers, sure, but trying to manage versions and settings and stuff, they are all over the place. Just try disabling the updater. it does what it wants anyway, and resets the settings on every update. We had an app that needed a specific version of chrome, yeah, that didn't work out. And don't get me started on their SSL cert crap!

On our networks, it is verboten!

OK... I'm stuck in the frozen tundra/prairie, and we're just lucky to have rabbit ears...
What is verboten?

Adjective
Forbidden, esp. by an authority

I should have said "Chrome is verboten"

I learned that one from Hogan's Heros.

[hal4uk]

Ahhhh... gotcha...

From an IT development standpoint...
Chrome observes web standards.
Chrome and FF are both generally (much) better than IE in that regard.
99% of everything that doesn't work ---- is an IE issue.

[FLBentRider]

Ahhhh... gotcha...

From an IT development standpoint...
Chrome observes web standards.
Chrome and FF are both generally (much) better than IE in that regard.
99% of everything that doesn't work ---- is an IE issue.

And they took it upon themselves to display an UGLY error message if you access a site with a "weak" (MD5 signed) ssl cert. Even if it is an INTERNAL app.

[squirtthecat]

Development vs Deployment will be a never ending headache/point of contention/battle..

'Nuff said.

[hal4uk]

Development vs Deployment will be a never ending headache/point of contention/battle..

'Nuff said.

Baby backs... and HACKS. Story of my life.  ::)