>>If you refer to an unscoped variable that doesn't exist, you're going to get an error, even though you wouldn't get an error from a nonexistent CGI
Exact, and this is precisely why i prefer to use unscoped cgi variables. I need to make a difference between undefined and blank variables. >>but CGI variables can differ between servers. Exact, but RFC clearly states that "A client MUST include a Host header field in all HTTP/1.1 request messages . If the requested URI does not include an Internet host name for the service being requested, then the Host header field MUST be given with an empty value. [...] All Internet-based HTTP/1.1 servers MUST respond with a 400 (Bad Request) status code to any HTTP/1.1 request message which lacks a Host header field" Then I suppose that IIS would reject requests with no host header, and if CF receives the call, then the header should exists. So I understand that the variable could contains nothing, but it still should be defined. This is the first time in several years I get this error, and I got a couple of ten in just a few seconds, so it must have come from some crap crawler, but I wonder how it could have come acrross. -- _______________________________________ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Check out the new features and enhancements in the latest product release - download the "What's New PDF" now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:284444 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
