Monday, September 10, 2012

problems like this with just-in-time collection server code with PivotViewer using httpS (SSL)?

problems like this with just-in-time collection server code with PivotViewer using httpS (SSL)?

We are working on an ASP.NET application at work that uses the just-in-time collection server code with PivotViewer. Everything works fine using plain http. However, the ASP.NET application requires users to login which means that it would be better if we use httpS ( SSL).

We needed to install Microsoft URL Rewrite Module http://www.iis.net/download/URLRewrite on the Server that hosts our application. We also added the following in our web.config to make the automatic 80 -> 443 redirection work

After the section, and this can not go anywhere else, the following code is added:

 <rewrite>   <rules>   <rule name="HTTP to HTTPS redirect" stopProcessing="true">   <match url="(.*)" />   <conditions>   <add input="{HTTPS}" pattern="off" ignoreCase="true" />   </conditions>   <action type="Redirect" redirectType="Found" url="https://{HTTP_HOST}/{R:1}" />   </rule>   </rules>   </rewrite>  

We have No web service, No WCF service, No ASMX Service.

However, when we deploy the application with httpS (SSL), the just-in-time collection server code with PivotViewer fails to show anything. There is No error. It just Fails to show anything.

Also, one of our Server Infrastructure technicians used fiddler to see if they can get more insight into the problem.

The following dzc url is requested twice in http, pictures load.

http://something.com/PivotResources-7fd9630b252c4ae794204f6b50b7ae06.dzc

But only once in https, pictures don't load.
https://something.com/PivotResources-70143ce2bf6149ff99656b21c9296eee.dzc

May I please know if anyone has had problems like this with just-in-time collection server code with PivotViewer using httpS (SSL)?  If so, could you please suggest how I would go about resolving this issue?

Answers & Comments...




No comments:

Post a Comment

Send us your comment related to the topic mentioned on the blog