Monday, September 27, 2010

chrome

Had to set up a little website and wanted to test it on my server which doesn't use port 80. Works great under Firefox, wanted to also test it in Chrome.

A few months ago a similar setup worked just fine, but it seems some c0der/suit/whatever got smart and now I get

The webpage at http://example.com:1234/ might be temporarily down or it may have moved permanently to a new web address. (Gee, really? It was there 30 seconds ago!)
More information on this error.
Below is the original error message
Error 312 (net::ERR_UNSAFE_PORT): Unknown error.

Hey, it's mah puter and I read whatever port I want, bitch!
Furthermore, it seems there's no easy way to disable this stupid behaviour.

Can I say "Fuck Chrome" on a Google-owned blogging platform? Ok, I won't say it.

LE: There actually is an easy way to enable a list of ports; my bad for stopping on "recompile from source" in the bug discussion. Thanks Lucian. Still stupid behaviour.

1 comment:

andreiolaru said...

Fuck Chrome! It thinks it is smarter than you and then you just clog it with extensions and crap.

I used it for many months, and it was close, but didn't make it into permanent use.