AnthonyRoberson
First Post
If you get an HTTP 500 error when you try to view the latest Dungeoncraft article, try it with Firefox or Chrome. I think somebody at WotC must hate Internet Explorer...
Latest Dungeoncraft Article
- Thread starter AnthonyRoberson
- Start date
catsclaw227
First Post
HTTP 500 errors should have nothing to do with your browser, unless the issue is some bizarre AJAX implementation. This is generally a server error and is browser independent.
I just checked and it's an Input past End of File error. Not sure why IE is getting this and not Firefox unless they are using some weird VBscript as a client language instead of javascript or something.
I just checked and it's an Input past End of File error. Not sure why IE is getting this and not Firefox unless they are using some weird VBscript as a client language instead of javascript or something.
mach1.9pants
Hero
Rightly so!
Quite likely their server code is having some conditional processing when the UserAgent is IE. And somebody made a mistake in that code.
It has happened now and then for over a year now. Usually when they add some new article to the system.
The worst part is that I registered a support ticket with CS about it... and got the response "Use FireFox instead". Problem solved.
I just re-opened the case and told them that I'm a paying customer with IE and I'm staying with IE. If they can't fix their bugs, they can just give me my money back.
catsclaw227
First Post
These EOF errors are trivial, though, and I am suprised that someone just hasn't give it a quick fix. There are loads of articles online that can show them how to do it.
I'm not so sure they are trivial, but since they've been around for over a year, any half-decent programmer would have been able to solve the problem by now.
I mean, come on, we know it's in line 494 of default.asp. Send the code to me and I'll fix it for you.
darkbard
Legend
Wow. That boggles the mind in an attempt to understand how that's customer service by any stretched definition of the word. It really irks me that this error is still not fixed. While, of course, I have no data to back this up, I assume some 90% of their clientele use IE, so one would hope that they would write code that actually serves that client base. Telling customers instead to use a different browser is unacceptable!
That's exactly what I told them.
I got a new response from CS. This time they are guessing it's a problem with an outdated version of QuickTime in my browser. But there is no code running in my browser! All my browser gets back from the server is HTTP Status 500 and the document:
Code:
Microsoft VBScript runtime error '800a003e'
Input past end of file
/default.asp, line 494They also added "it is beyond our ability to troubleshoot those specific issues". That I'm starting to believe...
wedgeski
Adventurer
On the other hand:
User: "When I try to access such and such page in IE, I get error XYZ."
CS: "Ah yes, we're aware of this and don't have a fix yet. In the meantime, you can successfully access the page using Firefox as a work-around."
...is perfectly acceptable.
It would be... if it wasn't for the fact that this same error has occurred on several occasions when they add a new article. It goes back well over a year, and that's unacceptable.
Anyway, the WotC tech team has arrived at work, and fixed the article. CS told me the tech team was aware of the broken article, so it was just a matter of getting them on the job.
So, everything is peachy... until they add the next article.
