bzr http protocol

[Max Bowsher]

On 21/10/10 15:04, Adrien Saladin wrote:
> Hi,
> 
> I still have a problem with interfacing the bzr wsgi application with
> the Pylons framework. After investigating and a lot of help from both
> Bazaar and Pylons community it seems there are two distinct problems.
> The first one comes from the bzr http protocol. When looking at the
> HTTP header, we can see that bzr sends an http POST that says it's
> x-www-form-encoded but tcp dumps tends to show that data is not
> encoded.
> Is this a bug or a feature ?
> (See http://pastebin.com/2FCuhF4q for a tcp dump of the http stream)

I'd call it a bug, but a really really mild one which shouldn't really
cause any problems.

> The second problem comes from Pylons itself (or one of the components
> it calls) that probably tries to enforce the encoding in some way that
> I can't revert it. I may have found a workaround for this problem.
> More on this later if someone is interested.

I'm no expert on WSGI, but wouldn't any tampering with the wsgi.input
stream be considered a bug in Pylons?

Max.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20101025/e6cf4eaa/attachment.pgp