Well... I figured it out. I wasn't going crazy, but the URLScan Tool was sure trying! URLScan is installed on our web servers, which is blocking the requests with the escaped ampersand. It simply returns a 404 error, but shows <rejected-by-urlscan> in the IIS logs.
My solution will probably be to restrict special characters in uploaded file names. "Kevin Aebig" <[EMAIL PROTECTED]> 06/08/2006 02:33 PM Please respond to cf-talk@houseoffusion.com To CF-Talk <cf-talk@houseoffusion.com> cc Subject RE: ampersand in file name Why not just swap out the character to a "_"? !k -----Original Message----- From: Terry L Schmitt [mailto:[EMAIL PROTECTED] Sent: June 8, 2006 12:18 PM To: CF-Talk Subject: OT: ampersand in file name I feel kinda goofy having to ask this... I have a forum that allows attachments and downloading. I use URLEncodedFormat() for the file name, but when a file contains an ampersand, the user just gets a 404 error when trying to dl the file. URLEncodedFormat() escapes the ampersand to %26 so the URL would be "test1%261%2Edoc". I've googled around and the consensus is that %26 should work, but it doesn't. Am I just going crazy or is this an IIS problem or should I just bite the bullet and not allow use of the ampersand character in uploaded file names? T ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:242985 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
