|
Home > Archive > IIS Server Security > August 2006 > iis 6 ssl issues
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Hi all,
We recently moved our asp.net to a new box running Windows 2003 SP1 and IIS
6. The site runs over SSL using a self-signed certificate and also uses
client certificates. Users are starting to see intermittent blank pages
and/or the notorious "Page cannot be displayed" message very frequently now.
At that point, if they simply go back and try again it works. This normally
happens on page post postbacks. What could be causing this? The older box
was on the same OS as well and everything worked fine.
TIA!
| |
|
| OK. Follow up to this post. Some users get a blank page on a page postback.
They have to close out of IE and then go back in and try the same page again
and everything works fine. Why is this happening? It is very frustrating to
end users.
TIA!
<param@community.nospam> wrote in message
news:O0SbEqEdGHA.3632@TK2MSFTNGP02.phx.gbl...
> Hi all,
>
> We recently moved our asp.net to a new box running Windows 2003 SP1 and
> IIS 6. The site runs over SSL using a self-signed certificate and also
> uses client certificates. Users are starting to see intermittent blank
> pages and/or the notorious "Page cannot be displayed" message very
> frequently now. At that point, if they simply go back and try again it
> works. This normally happens on page post postbacks. What could be causing
> this? The older box was on the same OS as well and everything worked fine.
>
> TIA!
>
| |
|
| Another follow up. It appears that randomly a http 413 error is causing this? This is what I found in the IIS logs for the website:-
2006-05-11 16:19:23 W3SVC2023926562 COLOWEB02 172.19.1.24 POST /tools/indirect/add_edit_stip.aspx id=84 443 - 172.19.1.50 HTTP/1.1 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) adminuserticket=042404FA0B6CB2C2E12C052D
C4223E229DD529751101CDC563E29AAB4C63492A
E0D7D193D254511EC46E69363CD7645C4DB2B12F
2177BD2A8EF96E33F78D946932A03DDB3E82729A
;+screenheight=1166;+membergroupnames=St
erling+Technologies,Sterling+Financial,A
dministrators,Risk+Managers,System+Admin
istrators,Multi- Company+Fax+Users,Customer+Support+Manag
ers;+membergroupids=2,3,5,14,18,22,23 https://moses.mydomain.net/tools/in...stip.aspx?id=84 moses.mydomain.net 413 0 0 166 1012 0
See the bolded error code above. What could be causing this?
TIA!
<param@community.nospam> wrote in message news:ulwKHMRdGHA.5116@TK2MSFTNGP02.phx.gbl...
> OK. Follow up to this post. Some users get a blank page on a page postback.
> They have to close out of IE and then go back in and try the same page again
> and everything works fine. Why is this happening? It is very frustrating to
> end users.
>
> TIA!
>
> <param@community.nospam> wrote in message
> news:O0SbEqEdGHA.3632@TK2MSFTNGP02.phx.gbl...
>
>
| |
| Daniel Schmitz 2006-06-04, 7:19 pm |
| Hi
i have the same problem with blank pages. I see also in IIS logs the status
413.
Can you solve this problem or find any reason which can explain this
behaviour?
| |
| jigs4u4ever 2006-08-09, 1:27 pm |
| Hi,
Your Web server thinks that the HTTP data stream sent by the client (e.g.
your Web browser or our CheckUpDown robot) was simply too large i.e. too many
bytes. What constitutes 'too many bytes' depends partly upon the operation
being attempted. For example a request to upload a very large file (via the
HTTP PUT method) may encounter a ceiling on upload file size set by the Web
server.
In your case i.e
adminuserticket=042404FA0B6CB2C2E12C052D
C4223E229DD529751101CDC563E29AAB4C63492A
E0D7D193D254511EC46E69363CD7645C4DB2B12F
2177BD2A8EF96E33F78D946932A03DDB3E82729A
;+screenheight=1166;+membergroupnames=St
erling+Technologies,Sterling+Financial,A
dministrators,R
isk+Managers,System+Administrators,Multi
-
The reson for the above to happen is either the web code is missing
something or is faulty or get corrupted or may be some problem with web
server related system files...
In simple the request send by client to the server is too large to get
handel by server.
Thanks & Regards
Jigs4u_4ever
"param@community.nospam" wrote:
> Hi all,
>
> We recently moved our asp.net to a new box running Windows 2003 SP1 and IIS
> 6. The site runs over SSL using a self-signed certificate and also uses
> client certificates. Users are starting to see intermittent blank pages
> and/or the notorious "Page cannot be displayed" message very frequently now.
> At that point, if they simply go back and try again it works. This normally
> happens on page post postbacks. What could be causing this? The older box
> was on the same OS as well and everything worked fine.
>
> TIA!
>
>
>
|
|
|
|
|