Skip to content

Comment on Twitter Said To Be Abandoning Ruby on Railsparent

Comments

Currently: 500 Internal Server Error.

(With an HTTP Status header being dumped to the screen instead of, you know, sent as a header.)

Do you obsessively check the headers for proper status codes whenever you land on a page? I'm always amazed how people find out header problems like this just by browsing.

He probably has firebug.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.