Re: [Xsltforms-support] Content negotiation problem: HTTP "Accept" header specifies non-XML content types

[Philip F. <Phi...@ma...>]

Efraim,

> The combine attribute, which can have the values "prepend", 
> "append", and "replace", does nothing.

Ahh, may be that is what I remember as not working.

Thanks for clarifying that.


Regards

Philip


-----Original Message-----
From: Efraim Feinstein [mailto:efr...@gm...] 
Sent: Friday, July 22, 2011 2:32 PM
To: xsl...@li...
Subject: Re: [Xsltforms-support] Content negotiation problem: HTTP "Accept" header specifies non-XML content types

Hi,

On 07/22/2011 09:07 AM, Conal Christopher Tuohy wrote:
> Hi Philip
>
> It would be nice if XSLTForms had a complete implementation of XForms 1.1, and if I could use the xf:header feature it would solve my problem, but I think for a 1.0 implementation it does still make sense not to accept a content-type of

Am I missing something? XSLTForms does support xf:header in trunk.

There does seem to be a bug in the implementation, though. Where the 
same header already exists, the XForms spec says that the value should 
be appended to the end. XSLTForms instead prepends it. The combine 
attribute, which can have the values "prepend", "append", and "replace", 
does nothing.


-- 
---
Efraim Feinstein
Lead Developer
Open Siddur Project
http://opensiddur.net
http://wiki.jewishliturgy.org


------------------------------------------------------------------------------
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks & Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...
https://lists.sourceforge.net/lists/listinfo/xsltforms-support