I have an ASP.Net app that when I do a button click and get the postback, I get this:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252"></HEAD>
<BODY></BODY></HTML>
This, obviously, is bogus. What could be doing this? (There should at least be Post back junk in the <body> tags.)
Other apps on the same server are not doing this. I have made no changes to the code.
-
-
Odd... check your log files. Is the status code for the request a 200?
-
Here it is:
2005-11-11 17:17:01 192.168.255.1 - 192.168.255.1 80 POST /errorwrapper/ErrorWrap.asmx - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+1.1.4322.2032)
-
/errorwrapper/ErrorWrap.asmx
Hmm.... -
qwert231 wrote:don't let the name fool you.
I have to admit, I was thrown.
Sorry, no ideas.
-
Sorry, that was the wrong one:
2005-11-11 17:35:15 192.168.255.1 CCL\mark 192.168.255.1 80 POST /internal/errorcollector.aspx - 400 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
2005-11-11 17:35:15 192.168.255.1 - 192.168.255.1 80 POST /internal/errorcollector.aspx - 401 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
-
Check if there is Response.End() if in the error handling page
-
qwert231 wrote:Sorry, that was the wrong one:
2005-11-11 17:35:15 192.168.255.1 CCL\mark 192.168.255.1 80 POST /internal/errorcollector.aspx - 400 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
2005-11-11 17:35:15 192.168.255.1 - 192.168.255.1 80 POST /internal/errorcollector.aspx - 401 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
Now we're cooking with gas...
400 is a "Bad Request" error
401 in particular is a "Unauthorized" error (authentication failed?)
Is there a #fields line at the top of the log file? That CCL\mark entry is interesting... is that the client computer name?
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.