Is it not possible to perform this 204 trick just by adding a new standard action that just sets the header and returns NONE? Similar to how the Redirect action works in WW1.x. One would then just chain to this action whenever one wants the header to be set? Would that work, or have I misunderstood something? Of course the HttpHeaderResult seems more flexible but perhaps also more complicated to implement.
Cheers, Dick Zetterberg [EMAIL PROTECTED] ----- Original Message ----- From: "Rickard Öberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 17, 2003 4:55 PM Subject: Re: [OS-webwork] HTTP 204 Trick > Jason Carreira wrote: > > So you don't think there should be a HttpHeaderResult to enable you to return > > special Http header codes? > > That's not what I said. I was talking about the result codes, not view > types. > > HttpHeaderResult seems fine to me. > ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
