On Hétf 2012. Márc 12 08:30:14, mark@summersault.com wrote:
Show quoted text> > I repeat, the problem which this bug report is about is that
> > param('POSTDATA') returns undef. I expect param('POSTDATA') to always
> > return the raw request body.
> >
> > I don't care at all about XForms. That spec can FOADIAF because it
> > hijacks a generic content-type.
>
> The way to convince me that that this is a bug is to use primary sources
> as references to show that some spec is being violated, or that the code
> is inconsistent with the documentation.
>
> Simply wishing it behaved differently that you expected is not enough.
>
> Mark
I'm with Daxim here.
1) the documentation does *not* mention the whole XForms shenanigans.
This is the gravest part of the issue, and thanks to that I've spent the
last few days banging my head to my desk because there was no bug on my
side that should have caused empty postdata.
2) XForms "support" (that you fill XForms:Model) doesn't appear to
interfere with normal postdata support. If you expect the XForms-using
people to mess with XForms:Model, then by all means they should do that,
and chances are they won't want to touch postdata; and vice versa, we,
the rest of the people who just want, say, and XML-RPC, we don't want to
touch XForms:Model. The data in both are the same -- the source code
comments themselves say that X:M contains the XML data untouched.
Simply, the two fields should point to the same data string and
everything will be happy.