• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

IIS returns 403 errors when accessing cfm pages via https but not over http

spyordie007

Diamond Member
I've got a bizarre issue on one of our web servers where if we try and pull up cfm pages over http they load and process correctly; however if we try and access the same page over https IIS is returning a 403 error.

We do not have this problem accessing any other kind of content (asp, aspx, html, jpg, etc.) over https. It only appears to be effecting cfm pages (IIS uses an ISAPI application mapping to Blue Dragon's dll - http://www.newatlanta.com/products/bluedragon/)

We have a couple other servers with very similar configurations that do not exibit this behavior.

This is an intranet server, however our userbase is fairly diverse geographically so we are trying to push users to use SSL to help with security.

If we review the IIS logs we simply see a 403.0 error. Here are the relevent logs for accessing a blank "test.cfm" in the root:
2005-09-07 15:04:30 client.ip DOMAIN\USER server.ip 80 GET /test.cfm - 200 0 15562 597 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
2005-09-07 15:04:32 client.ip DOMAIN\USER server.ip 443 GET /test.cfm - 403 0 646 2536 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)

2000 Server SP4 (IIS 5.0)

Thanks in advance for any comments, suggestions, etc.,

-Erik
 
Interesting; we are running the free version on this server. I wasnt aware of their support (we've never seen a licensing error on this or any of the other servers and I dont think they used to license it this way) however this could be the case since this server followed a slightly differant install path (it started at 6.2 and the other servers were upgraded to 6.2 from older versions).

I'll go from here, thanks for the catch Chad.

-Erik
 
Back
Top