[issue3244] multipart/form-data encoding

[Martin Panter]

Martin Panter added the comment:

I think encoding the user’s IP address into the boundary is a bad idea. 
Forest’s version uses the existing “email” package, which calls 
random.randrange(sys.maxsize) and searches through the data for conflicts.

I haven’t really researched this, but I suspect it would be even better to use 
a CSPRNG like the new “secrets” module, or uuid.uuid4(). Otherwise, perhaps 
there is the possibility of attacks by predicting the boundary and injecting 
HTTP headers, splitting up requests, etc via a file upload.

Both Forest and Senthil’s patches look like they load all the data into memory, 
so would not be useful for streaming, which was the original request. Hence I 
am putting this back to “needs patch”. Issue 3243 has been resolved, meaning 
that we can stream upload data as long as the Content-Length has been 
pre-calculated. The length could be calculated based from the length of each 
piece (e.g. file sizes).

Also, with Issue 12319 (chunked encoding) about to be resolved, if people only 
need to use HTTP 1.1, it may be easier to upload forms using chunked encoding, 
where you don’t have to worry about Content-Length.

--
stage: patch review -> needs patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[SilentGhost]

Changes by SilentGhost :


--
Removed message: http://bugs.python.org/msg272583

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[SilentGhost]

Changes by SilentGhost :


--
nosy: +Chris.Waigl, Johannes.Hoff, ajaksu2, alexz, atommixz, barry, bgamari, 
catalin.iacob, catlee, cco3, checat, daniel.ugra, eric.araujo, forest_atq, 
fsteinel, gotgenes, guettli, jnoller, martin.panter, orsenthil, 
piotr.dobrogost, pitrou, r.david.murray, raylu, shazow, tamentis -lissacoffeyx

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[lissacoffeyx]

lissacoffeyx added the comment:

In principle I think something like this should go in.  Since it is a Message 
subclass, I'd like it to follow the current Message API whether or not it is 
located in the email package.  __str__ and as_string have the right default for 
line length (no folding).  The current default for line endings is \n, and I 
think the class should stick with that.  You can't use __str__ or as_string to 
generate what you send on the wire if you are supporting binary data.

I am planning additions to the email API that will make integrating this class 
and adjusting the generated line endings easier.  For the latter (assuming the 
email-sig approves) I plan a __bytes__ method that will generate "wire format", 
which would include using \r\n line endings and should be just what you need.

The current email package does not support the binary content transfer 
encoding, only 8bit.  Support for the binary CTE is another planned addition 
for 3.3, and I think it can be prioritized ahead of most other features, given 
that this code needs it.

So, you might want to wait until the email pieces are in place, and possibly 
even help me develop them :) http://qwikfix.co.uk/sky-customer-services/

--
nosy: +lissacoffeyx -Chris.Waigl, Johannes.Hoff, ajaksu2, alexz, atommixz, 
barry, bgamari, catalin.iacob, catlee, cco3, checat, daniel.ugra, eric.araujo, 
forest_atq, fsteinel, gotgenes, guettli, jnoller, martin.panter, orsenthil, 
piotr.dobrogost, pitrou, r.david.murray, raylu, shazow, tamentis

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[raylu]

Changes by raylu :


--
nosy: +raylu

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Martin Panter]

Changes by Martin Panter :


--
nosy: +vadmium

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Piotr Dobrogost]

Changes by Piotr Dobrogost :


--
nosy: +piotr.dobrogost

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Ezio Melotti]

Changes by Ezio Melotti :


--
versions: +Python 3.4 -Python 3.3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Hi Senthil Kumaran,

Thanks for the feedback & patch.

I agree having support in urllib probably makes some sense. But why not 
implement basic support elsewhere and then tie it into urllib so those of us 
using something else can also use it? I'm using httplib in my application.

Thanks,
Forest

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Senthil Kumaran]

Senthil Kumaran  added the comment:

Thanks for the patch, Forest Bond. 

However, the way I look at this feature, it could be added into  urllib.request 
as a separate handler called MultiPostHandler and request object when it 
requires it should be able to add it and then use it.
Here is a first version of this patch, which would give the idea of how it 
would be added to the urllib.request (Note this is python3 adaptation of PyPi 
package by name MultipartPostHandler). I shall see to add this in 3.3 and shall 
include the tests/docs/howto.

--
Added file: http://bugs.python.org/file26146/Issue3244.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[R. David Murray]

R. David Murray  added the comment:

Thanks.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Okay, Contributor Agreement sent.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Sure thing. I'll send it via e-mail later today.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[R. David Murray]

R. David Murray  added the comment:

Forest, could you please submit a contributor agreement?

http://www.python.org/psf/contrib/

Life caught up with me and I haven't made enough progress to do anything with 
this yet, but I still want to.

--
assignee: r.david.murray -> 
components: +email -Library (Lib)
stage: test needed -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Ugra Dániel]

Changes by Ugra Dániel :


--
nosy: +daniel.ugra

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Aleksey Frolov]

Changes by Aleksey Frolov :


--
nosy: +atommixz

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Conley Owens]

Changes by Conley Owens :


--
nosy: +cco3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Hi, Johannes.  You can assume the Python license for this patch.

-Forest

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Johannes Hoff]

Johannes Hoff  added the comment:

Forest Bond: Thanks for this patch - I hope it will go in soon. In the 
meantime, could I get permission to use it as is? (I notice there is a 
copyright in the file) I would of course keep the attributions in the file.

--
nosy: +Johannes.Hoff

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Catalin Iacob]

Changes by Catalin Iacob :


--
nosy: +catalin.iacob

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[R. David Murray]

R. David Murray  added the comment:

In principle I think something like this should go in.  Since it is a Message 
subclass, I'd like it to follow the current Message API whether or not it is 
located in the email package.  __str__ and as_string have the right default for 
line length (no folding).  The current default for line endings is \n, and I 
think the class should stick with that.  You can't use __str__ or as_string to 
generate what you send on the wire if you are supporting binary data.

I am planning additions to the email API that will make integrating this class 
and adjusting the generated line endings easier.  For the latter (assuming the 
email-sig approves) I plan a __bytes__ method that will generate "wire format", 
which would include using \r\n line endings and should be just what you need.

The current email package does not support the binary content transfer 
encoding, only 8bit.  Support for the binary CTE is another planned addition 
for 3.3, and I think it can be prioritized ahead of most other features, given 
that this code needs it.

So, you might want to wait until the email pieces are in place, and possibly 
even help me develop them :)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Hi,

So is the following enough to get this applied?  If so, I'm game.

* Review RFC and enforce Content-Encoding: binary if applicable [checat].
* Generate CR+LF line endings [checat].
* Review RFC and address "line-splitting and header-folding" if applicable 
[checat].
* Write documentation.

I can have this done in a week or so, but I'd like to have some confidence that 
it will be applied if I spend the time on it.

Thanks,
Forest

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Jesse Noller]

Jesse Noller  added the comment:

Yeah, despite what the RFC says, the most common usage is in web clients, and 
stuffing it in the email module won't be obvious to 95% of the population I 
think, unless that's where the implementation lives, but we can add a doc stub 
in the http docs pointing to it and why.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[R. David Murray]

R. David Murray  added the comment:

This patch needs a Doc component.

Having finally taken a quick look at the RFC (I haven't read it through yet), I 
think this does belong in email and not http.  The RFC makes it clear that 
while the most common implementation is http, it is designed to be generic, and 
as such IMO the logical place for it in the stdlib is with the rest of the MIME 
types, in email.  From a usability standpoint, however, it would be more 
convenient in http, so if most people think it should go into http I won't 
object.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Looks like bgamari and I stepped on each other's requests.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Hi,

Sorry for the long delay.  I have tested against a Python web application using 
restish via various WSGI web servers (CherryPy, wsgiref) and I have not seen 
problems.  It may cause problems with other server-side implementations.

I will not have time to do broad testing against many different server-side 
implementations.  Is there harm in applying the patch and fixing bugs that get 
reported?

Thanks,
Forest

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Ben Gamari]

Ben Gamari  added the comment:

Has there been any progress here?

--
nosy: +bgamari

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[R. David Murray]

Changes by R. David Murray :


--
versions: +Python 3.3 -Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Chris Waigl]

Changes by Chris Waigl :


--
nosy: +Chris.Waigl

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Konstantin Pelepelin]

Konstantin Pelepelin  added the comment:

Did you test it against server-side form-data parser implementation? It will be 
useless if it won't work with most widespread implementations: PHP's and at 
least some others (consider some popular python web frameworks). 

MIME-compliance is not enough, because browsers send only subset of MIME format 
and server-side parsers don't expect bodies full of MIME features.

Particularly, I believe, most implementations don't expect any 
"Content-Transfer-Encoding", except "binary", because only 8-bit transfers are 
implemented in browsers, also you should check there will be no line-splitting 
and header-folding in headers and content, and make sure CR+LF (not plain LF, 
which is in patch) is always used.

--
nosy: +checat

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

I don't think Python trunk has the encoders issue, as that is related to the 
base64 moving to the bytes type.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

See issue8896 for email.encoders fix.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

New patch:

* Renames class to FormData.
* Replaces method get_body with get_request_data to simplify semantics.
* Drops changes to email.encoders.  I'll create a new ticket to deal with that 
bug.  Note that tests here fail without that fix.

--
Added file: http://bugs.python.org/file17548/http_formdata.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Hm, there is one issue.  The example in the docstring wouldn't work.

You have to get the headers *after* the body, because the boundary isn't 
generated until the body has been.  So this would work:

  body = msg.get_body()
  headers = dict(msg)

But this won't:

  headers = dict(msg)
  body = msg.get_body()

I'm not sure what the best way to deal with this is.  Maybe instead of get_body 
we should have get_request_data which returns both headers and body.  That 
would provide simpler semantics.

Thoughts?

Thanks,
Forest

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Éric Araujo]

Éric Araujo  added the comment:

Would you please open another issue for the email fix? Bonus points if you test 
it on trunk too, since release candidate happens in some days :)

Do you people think we could unify client and server-side code in the new 
module (with an alias from cgi for b/w compat), to prevent endless questions?

Minor remark: I think we don’t have to follow the email naming scheme here. A 
simpler name like FormData could be just fine.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Here's a new patch.

--
Added file: http://bugs.python.org/file17547/http_formdata.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Éric,

Sorry, I just read your message.

I'll post a new patch with a module docstring.

I believe cgi.FieldStorage is only useful for parsing (i.e. on the server 
side).  MIMEMultipartFormData is for generating multipart/form-data messages 
(i.e. on the client side).

Thanks,
Forest

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Hi,

Patch attached.  Let me know what needs fixing.

I had to fix a bug in email.encoders for my tests to pass.  I have not run the 
full test suite at this point (need to build py3k to do that, maybe I'll have 
time later today, but if someone else has time, feel free).

Thanks,
Forest

--
keywords: +patch
Added file: http://bugs.python.org/file17546/http_formdata.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Éric Araujo]

Éric Araujo  added the comment:

Seems good to me, as long as the module docstring clearly stats whether it’s 
useful for the client side, the server side or both.

BTW, isn’t there overlap with cgi.FieldStorage?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

As http.formdata?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Éric Araujo]

Éric Araujo  added the comment:

I think it belongs in the http package.

--
nosy: +merwok

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Should the module be called rfc2388 or should it go into email.mime as 
formdata?  It seems odd to put something HTML/HTTP related into email.mime, but 
maybe that would be fine.  In any case, httplib docs should probably point to 
this module with an example, right?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Okay, I'll submit against py3k.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> I haven't yet touched Python 3.0, and may not have time to dig in at
> the moment.  It wouldn't be suitable to provide a patch against 2.7?

2.7 is almost in release candidate phase, which means it's much too late
for new features now.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

I haven't yet touched Python 3.0, and may not have time to dig in at the 
moment.  It wouldn't be suitable to provide a patch against 2.7?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Antoine Pitrou]

Antoine Pitrou  added the comment:

You should write your patch against Python 3.x (py3k).

--
nosy: +pitrou

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Oh, hm, looks like I left a hard-coded name="files" in attach_file.  I'll fix 
that in the patch after I've received any other feedback.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Forest Bond]

Forest Bond  added the comment:

Hi,

I believe the attached implementation is reasonable.  I'm not sure if it should 
be called "email.mime.formdata", "rfc2388", etc.

I'd be happy to attach a proper patch with tests given some quick feedback.

Thanks,
Forest

--
nosy: +forest_atq
Added file: http://bugs.python.org/file17543/rfc2388.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[R. David Murray]

Changes by R. David Murray :


--
assignee:  -> r.david.murray
versions: +Python 3.2 -Python 2.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Barry A. Warsaw]

Changes by Barry A. Warsaw :


--
assignee: barry -> 

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[R. David Murray]

R. David Murray  added the comment:

Daniel suggested marking this as superseding issue 727898, and I agree.  But I 
want to note that in that issue Barry suggested that it was possible services 
from the email package could be useful in building this support, and that there 
might be a better place for it to live than urllib.

--
nosy: +r.david.murray

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Thomas Guettler]

Changes by Thomas Guettler :


--
nosy: +guettli

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Jesse Noller]

Jesse Noller  added the comment:

This request really does need a patch+tests+doc changes - I don't know if 
anyone with +commit has the time to distill the various implementations 
and generate something.

--
nosy: +jnoller

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Andrey Petrov]

Andrey Petrov  added the comment:

Once upon a time I wrote a library that did some of this among other things:

http://code.google.com/p/urllib3/

Or specifically:
http://code.google.com/p/urllib3/source/browse/trunk/urllib3/filepost.py

The code was borrowed from some of the recipes mentioned, but cleaned up
and adjusted a bit. Feel free to use it or borrow from it in any way you
like.

--
nosy: +shazow

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Bertrand Janin]

Changes by Bertrand Janin :


--
nosy: +tamentis

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Alex Z.]

Changes by Alex Z. :


--
nosy: +alexz

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Barry A. Warsaw]

Changes by Barry A. Warsaw :


--
assignee:  -> barry
nosy: +barry

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Daniel Diniz]

Changes by Daniel Diniz :


--
priority:  -> normal

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Daniel Diniz]

Changes by Daniel Diniz :


--
dependencies: +Support iterable bodies in httplib
keywords: +easy
nosy: +orsenthil
stage:  -> test needed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Daniel Diniz]

Daniel Diniz  added the comment:

So, what is the best way to go about this (beyond docs and tests)? Beat
the linked recipe into a patch, adapt Chris' implementation?

--
nosy: +ajaksu2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Chris Lasher]

Changes by Chris Lasher :


--
nosy: +gotgenes

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Chris AtLee]

Chris AtLee <[EMAIL PROTECTED]> added the comment:

I also wrote some software to handle this:
http://atlee.ca/software/poster/poster.encode.html

The reason I wrote this is to avoid having the load the entire file into
memory before posting the request.

This, along with Issue #3243, would allow streaming uploads of files via
HTTP POST.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Florian Steinel]

Florian Steinel <[EMAIL PROTECTED]> added the comment:

see http://code.activestate.com/recipes/146306/ for a user contributed
implementation.

--
nosy: +fsteinel

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3244] multipart/form-data encoding

[Chris AtLee]

New submission from Chris AtLee <[EMAIL PROTECTED]>:

The standard library should provide a way to encode data using the
standard multipart/form-data encoding.

This encoding is required to support file uploads via HTTP POST (or PUT)
requests.

Ideally file data could be streamed to the remote server if httplib
supported iterable request bodies (see issue #3243).

Mailing list thread:
http://mail.python.org/pipermail/python-dev/2008-June/080783.html

--
components: Library (Lib)
messages: 69015
nosy: catlee
severity: normal
status: open
title: multipart/form-data encoding
type: feature request
versions: Python 2.7

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com