the server responses to .cfm requests (even to not found files) always 
include a blank line in between the Server: header and the Content-type: 
header. This blank line gets interpreted as the end of the header, hence 
the extraneous characters at the top of the page. In addition, your 
homepage (index.cfm) sends a Content Location: header, which should be 
Content-Location:

The reason your users can't log in is they never receive the Set-Cookie: 
response headers as they are interpreted as part of the body, not part of 
the header.

It does all look like a CFCONTENT or CFHEADER problem, not anything to do 
with URLScan, IIS or any other ISAPI filters (the server response to 
requests for non-.cfm files is fine). I could be wrong though, if some of 
the ISAPI filters are taking action for .cfm requests that they are not 
taking for other requests.

Would be very interested to know more about the problem and if you have 
found a solution, what it was.


Mark


>Content-type: text/html
>Page-Completion-Status: Normal
>Page-Completion-Status: Normal
>Set-Cookie: CFID=513; expires=Sun, 27-Sep-2037 00:00:00 GMT; path=/;
>Set-Cookie: CFTOKEN=43849660; expires=Sun, 27-Sep-2037 00:00:00 GMT; path=/;
>
>
>Those are the response header name/value pairs. There's a problem with your
>Application.cfm template. As you probably noticed, your CFIDs and CFTOKENs
>are changing on every refresh - which should not be happening unless
>setdomaincookies are ON. However, this is not the case since CFMAGIC is not
>present in the response header.
>DO a global search on '09/27/2037' or '27-Sep-2037' this should point you
>in the right direction.
>
>PT
>
______________________________________________________________________
This list and all House of Fusion resources hosted by CFHosting.com. The place for 
dependable ColdFusion Hosting.
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with 
'unsubscribe' in the body or visit the list page at www.houseoffusion.com

Reply via email to