Re: [Django] #34522: PUT/PATCH data is not encoded for multipart/form-data in Django Test Client

2023-04-27 Thread Django 
#34522: PUT/PATCH data is not encoded for multipart/form-data in Django Test 
Client
-+-
 Reporter:  Matej Mijoski|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  4.2
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  multipart form   | Triage Stage:
  data, tests, put data encoding |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Yes, it's intentional. Duplicate of #12635 (see comments and related
 discussions for more details.)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070187c270e211-8fd8fa73-38ad-47b1-b51b-ac08f93dc3f8-00%40eu-central-1.amazonses.com.

Re: [Django] #34522: PUT/PATCH data is not encoded for multipart/form-data in Django Test Client (was: PUT/PATCH data is not encoded for multipart/form-data in Django Test)

2023-04-27 Thread Django 
#34522: PUT/PATCH data is not encoded for multipart/form-data in Django Test 
Client
-+-
 Reporter:  Matej Mijoski|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  multipart form   | Triage Stage:
  data, tests, put data encoding |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070187c25f3c9e-32952c1b-5559-4d59-b9d9-5270645eacad-00%40eu-central-1.amazonses.com.

Re: [Django] #34522: PUT/PATCH data is not encoded for multipart/form-data in Django Test

2023-04-27 Thread Django 
#34522: PUT/PATCH data is not encoded for multipart/form-data in Django Test
-+-
 Reporter:  MatejMijoski |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  multipart form   | Triage Stage:
  data, tests, put data encoding |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by MatejMijoski:

Old description:

> I've noticed that the mulipart/form-data is only encoded in the POST
> request of the Django test client and not in the PUT/PATCH requests. Is
> this intentional and if so, why?

New description:

 I've noticed that when making a request using the Django test client with
 a multipart/form-data content type, the data only gets encoded for POST
 requests. Is intentional and if so, why?

--

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070187c25da9ff-e1754b3d-06b8-4fc0-8dc4-ac024e7bd2f5-00%40eu-central-1.amazonses.com.

[Django] #34522: PUT/PATCH data is not encoded for multipart/form-data in Django Test

2023-04-27 Thread Django 
#34522: PUT/PATCH data is not encoded for multipart/form-data in Django Test
-+-
   Reporter: |  Owner:  nobody
  MatejMijoski   |
   Type:  Bug| Status:  new
  Component:  Testing|Version:  4.2
  framework  |   Keywords:  multipart form
   Severity:  Normal |  data, tests, put data encoding
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I've noticed that the mulipart/form-data is only encoded in the POST
 request of the Django test client and not in the PUT/PATCH requests. Is
 this intentional and if so, why?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070187c25bebec-69ad4801-a2df-4448-b9c4-48180fb594ab-00%40eu-central-1.amazonses.com.