[Exist-open] [ exist-Bugs-1784594 ] response:set-header() vs xquery serialize pragma

[SourceForge.net <no...@so...>]

Bugs item #1784594, was opened at 2007-08-30 06:28
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=117691&aid=1784594&group_id=17691

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: jamesfuller2007 (jamesfuller2007)
Assigned to: Nobody/Anonymous (nobody)
Summary: response:set-header() vs xquery serialize pragma

Initial Comment:
I noticed an interesting situation when trying to set mime-type with an HTTP response from RESTful interface (latest trunk), from within my xquery. 

initially, I tried to use response:set-header('Content-type: application/xml') to set the header on the output with no joy. Is this supposed to work or is there some sort of hidden conflict  or assumed processing precedence (for example from cocoon, or config settings)

I then decided to use a serialize pragma

declare option exist:serialize "media-type=application/xml";

which gave me the right mime type.

cheers, Jim Fuller




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=117691&aid=1784594&group_id=17691