Jochem also helped me with this a year, or so, back.  204 was exactly
what I needed when I wanted a link to perform an action, but not change
the browser.  I'm glad he has memorized every RFC.

M!ke 

-----Original Message-----
From: Ali Awan [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 01, 2006 3:17 PM
To: CF-Talk
Subject: Re: how to send a null response header in http

Jochem,

Thanks!  That worked like a charm!
All I needed to do was add that snippet sending back a 204 Response
Header.

Take care,
Ali

>
>They will always get a HTTP response back, there is no way around that 
>because that is how HTTP is defined:

>The best thing to do is using cfheader to send a HTTP 204 "No Content" 
>status code back:
><cfcontent reset="yes"><cfheader statuscode="204"><cfabort>

>Jochem

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:239221
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

Reply via email to