G
Guest
I have a 3 page ASP.NET web application that is using an asp:Wizard control
on the main page. There is no authentication (completely open) and all
processesing is done on this single page. I have a master page that has all
of the application layout to match our corporate look and feel and a folder
called "HBW" under "App_Themes" in the web directory containing 15 style
sheets that were copied over from our corporate site.
On our local development machines everything works as expected and in our QA
environment everything worked as expected, however once we launched to
production, we were getting reports that every once in a while a user would
get a page that would be completely white, without any of the images,
background colors, etc.
After several attempts at reproducing the issue in QA, we finally set up a
QA environment with the same SSL certificate as we were using in production
and violla! we were able to reproduce the problem, however there was nothing
in the Application or System logs and no errors in our own application's
internal logging that would indicate that an error or exception had ocurred
to cause it.
It seems to occur on no particular step of the wizard and does not happen
every time. If we get the issue and then click next, previous, or refresh the
screen the styles reload just fine and so far we have only gotten it to
re-occur on that particular page. When we view the source code of the page
when it faults everything looks in place except that all of the style sheets
and theme applied image paths are missing, which tells me directly that
somehow the ASP.NET theme rendering is breaking during the page life-cycle.
Is there something I am missing?
We do not have smart navigation turned on as that was the first thing I
checked. We are also not using AJAX although we are using some Infragistics
data edit controls.
We currently have 3 other rather complex web applications in the same
environment using a copy of the exact same theme, also using one or more
wizard controls and 2 of which are using AJAX, Infragistics and a slurry of
other technologies without any issues similar to this.
The only thing we can find that seems to consistently cause this behavior to
occur in this application, albeit sporradic, is when we enable SSL in IIS and
access the application using https://.
Any help on this would be greatly appreciated as we are banging our heads
against the wall trying to figure this out.
on the main page. There is no authentication (completely open) and all
processesing is done on this single page. I have a master page that has all
of the application layout to match our corporate look and feel and a folder
called "HBW" under "App_Themes" in the web directory containing 15 style
sheets that were copied over from our corporate site.
On our local development machines everything works as expected and in our QA
environment everything worked as expected, however once we launched to
production, we were getting reports that every once in a while a user would
get a page that would be completely white, without any of the images,
background colors, etc.
After several attempts at reproducing the issue in QA, we finally set up a
QA environment with the same SSL certificate as we were using in production
and violla! we were able to reproduce the problem, however there was nothing
in the Application or System logs and no errors in our own application's
internal logging that would indicate that an error or exception had ocurred
to cause it.
It seems to occur on no particular step of the wizard and does not happen
every time. If we get the issue and then click next, previous, or refresh the
screen the styles reload just fine and so far we have only gotten it to
re-occur on that particular page. When we view the source code of the page
when it faults everything looks in place except that all of the style sheets
and theme applied image paths are missing, which tells me directly that
somehow the ASP.NET theme rendering is breaking during the page life-cycle.
Is there something I am missing?
We do not have smart navigation turned on as that was the first thing I
checked. We are also not using AJAX although we are using some Infragistics
data edit controls.
We currently have 3 other rather complex web applications in the same
environment using a copy of the exact same theme, also using one or more
wizard controls and 2 of which are using AJAX, Infragistics and a slurry of
other technologies without any issues similar to this.
The only thing we can find that seems to consistently cause this behavior to
occur in this application, albeit sporradic, is when we enable SSL in IIS and
access the application using https://.
Any help on this would be greatly appreciated as we are banging our heads
against the wall trying to figure this out.