- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Looks like the 455 error page was added to the website 12 days ago: github.com/tdwtf/WtfWebApp/commit/28... :grinning:
Admin
I read TDWTF on RSS since the last site design, and I actually checked the main page for this one to make sure that Alex wasn't serving up that to people the server thought were hotlinking. Because that would have been a WTF.
Admin
Admin
Right here I can see the text input on my tablet. Seriously, Discourse is a WTF on its own.
Steve, didn't you post exactly the same comment on the Perl post from yesterday or so?
Admin
You've been a member for 6 months, and you just noticed?
Admin
Mostly the same, not exactly the same, but yes.
Admin
To be honest, I have no big issues on my PC but recently started using my tablet to browse TDWTF. The problems I encounter on there are a lot more serious.
Admin
I viewed it on the website and I still thought it was a hotlinking error.
Admin
I read this differently - did the developer really want a 404 page on the IRS site to run his JS?
The webapp(?) was I presume running on an internal Innotek server; maybe the Apache server run by Mike?. It has a link in some application that points to an external end-point that can't be changed easily (I am being generous here).
Maybe there was some confusion about Apache URL re-writing rules for incoming links, but would be entirely possible to have a proxy like Squid or Fiddler to intercept and rewrite the outgoing URL to correct it outside of code. As an ugly hack for development only.
The use of a 404 page as an option I can't understand, but who knows what the developer (as relayed by the PM), was really thinking. Can't imagine it would be adding a 404 page to the IRS site, but maybe they were considering detecting a 404 response from the IRS, and redirecting the browser to an internal 404 page where... uggh that just makes no sense compared with just fixing the code.
The real WTF; why did Mike not just bypass the relatively non technical Project Manager and talk directly to the Developer (Jay) and understand why the hell the URL in the app is not just fixed. I can't imagine code in which an external URL can't be changed.