[Featureserver] [PATCH] handle multipart POSTs
crschmidt at metacarta.com
Wed Jan 16 19:19:48 EST 2008
On Wed, Jan 16, 2008 at 06:30:52PM -0500, Dan Lipsitt wrote:
> On Jan 16, 2008 5:30 PM, Christopher Schmidt <crschmidt at metacarta.com> wrote:
> > This only adjusts the wsgi handler. Is this a problem specifically for
> > that handler for some reason?
> It may be present in the other handlers, but I'm not using them right
> now. The logic that was broken was in the wsgi handler, but perhaps it
> could be factored out and used for all of them.
> > Can you explain how I encounter misbehavior this fixes?
> It was treating multipart boundaries as part of the uploaded file.
> Notably, the php Request module builds multipart POST.
I guess the problem I'm having, conceptually, is that you're not
uploading *files*, you're POSTing *strings*, and I'm confused why it
would be doing multipart POST for that. Can I see some example code that
I could cause it to reproduce with? (No need for it immediately, but I
want to make sure I really understand first.)
It's possible that this is an 'enhancement', rather than 'bug', in
ticket tracking speak. If that's the case, I think I understand it and
it makes sense. If it's a 'bug', then I don't understand it.
In either case, it's somewhat important to me to make all three (wsgi,
mod_python, cgi) support the same level of functionality, so someone
will need to hack the support into the other two handlers: I'll add this
to my todo list to do if no one else gets to it first.
> It's read-only. I implemented handle_post() for item creation.
Hm, I'd take a patch, though I'd then have to change the WFS -> GML,
since WFS 'creation' is WFS-T, which I'm assuming isn't what you
implemented. That's not really a problem, just me talking out loud.
More information about the Featureserver