date:20220309

Re: [Django] #33569: Add support for multiple values for the x-forwarded-proto header

2022-03-09 Thread Django

* status: assigned => closed
* resolution: => wontfix

Comment:

As far as I'm aware, we cannot answer in the reliable way whether the
request was over HTTPS, when `X-Forwarded-Proto` contains multiple values.
Unfortunately it depends on which layer is trusted. We could check if all
values are "https", but this could be unacceptable with in-companies
proxies. It's definitely not enough to check if "https" is used somewhere
in the pipeline.

As a workaround you can set list of protocols in the
`SECURE_PROXY_SSL_HEADER`, e.g. `SECURE_PROXY_SSL_HEADER =
("HTTP_X_FORWARDED_PROTO", "https,http")`. I don't think it's worth
additional complexity. You can start a discussion on DevelopersMailingList
if you don't agree.

--
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/0107017f72c70aa1-4e40bb3c-c48a-4bfc-89f4-4006768f8c8d-00%40eu-central-1.amazonses.com.

Re: [Django] #31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method.

2022-03-09 Thread Django

#31169: Allow parallel test runner to work with Windows/macOS `spawn` process 
start
method.
-+-
 Reporter:  Brandon Navra|Owner:  David
 |  Smith
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


-- 
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/0107017f72b52ac2-7eef503c-6d16-4740-9f00-8f6cde0580f8-00%40eu-central-1.amazonses.com.

Re: [Django] #33569: Add support for multiple values for the x-forwarded-proto header

2022-03-09 Thread Django

#33569: Add support for multiple values for the x-forwarded-proto header
-+-
 Reporter:  Thomas Schmidt   |Owner:  Thomas
 Type:   |  Schmidt
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Thomas Schmidt
 * needs_better_patch:  0 => 1
 * status:  new => assigned


-- 
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/0107017f72842655-a8ab974c-3313-40f9-9d89-72cbc5502155-00%40eu-central-1.amazonses.com.

Re: [Django] #30923: Out of date examples in docs that call render() with a Context instance instead of regular dict

2022-03-09 Thread Django

#30923: Out of date examples in docs that call render() with a Context instance
instead of regular dict
-+-
 Reporter:  Alasdair Nicol   |Owner:  (none)
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Context render   | Triage Stage:  Accepted
  template   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Old description:

> Following #30906, I found a couple more examples in the docs that are
> calling the template's render method with a Context instance when they
> should use a regular dict.
>
>  * [https://docs.djangoproject.com/en/2.2/ref/contrib/sites/#getting-the-
> current-domain-for-display docs/ref/contrib/sites.txt ] - I will open a
> pull request for this
>  * [https://docs.djangoproject.com/en/2.2/howto/custom-template-tags
> /#auto-escaping-considerations howto/custom-template-tags.txt] - I am not
> sure how to rewrite this example.
>
> I found these by searching with the following commands:
>
> {{{
> cd docs
> git grep 'render.*Context'
> git grep 'from django.*import.*Context'
> }}}
>
> Those grep commands also return results from `ref/templates/api.txt`, but
> they are ok because they use `t = Template()` instead of
> `loader.get_template()`.

New description:

 Following #30906, I found a couple more examples in the docs that are
 calling the template's render method with a Context instance when they
 should use a regular dict.

  * [https://docs.djangoproject.com/en/2.2/ref/contrib/sites/#getting-the-
 current-domain-for-display docs/ref/contrib/sites.txt ] - I will open a
 pull request for this
  * ~~[https://docs.djangoproject.com/en/2.2/howto/custom-template-tags
 /#auto-escaping-considerations howto/custom-template-tags.txt] - I am not
 sure how to rewrite this example.~~

 I found these by searching with the following commands:

 {{{
 cd docs
 git grep 'render.*Context'
 git grep 'from django.*import.*Context'
 }}}

 Those grep commands also return results from `ref/templates/api.txt`, but
 they are ok because they use `t = Template()` instead of
 `loader.get_template()`.

--

Comment:

 Examples in `howto/custom-template-tags.txt` work with `Context()`.
 Closing as fixed.

-- 
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/0107017f72658b6a-dcda8d3e-f860-4010-b0e0-72f1e26c894a-00%40eu-central-1.amazonses.com.

Re: [Django] #32604: File uploads larger than FILE_UPLOAD_MAX_MEMORY_SIZE get wrong unix group based on setgid

2022-03-09 Thread Django

#32604: File uploads larger than FILE_UPLOAD_MAX_MEMORY_SIZE get wrong unix 
group
based on setgid
-+-
 Reporter:  Gavin Wahl   |Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  File |  Version:  3.1
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mateo Radman):

 * owner:  nobody => Mateo Radman
 * status:  new => assigned


-- 
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/0107017f70c10a83-7419da6c-030a-48c3-aa58-07c745f6b349-00%40eu-central-1.amazonses.com.

Re: [Django] #30923: Out of date examples in docs that call render() with a Context instance instead of regular dict

2022-03-09 Thread Django

#30923: Out of date examples in docs that call render() with a Context instance
instead of regular dict
-+-
 Reporter:  Alasdair Nicol   |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  Context render   | Triage Stage:  Accepted
  template   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sean Bermejo):

 * has_patch:  0 => 1


Comment:

 I created a PR for the custom template tags docs:
 https://github.com/django/django/pull/15495

-- 
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/0107017f6f8a295e-aa32a17d-1a1a-4a23-9688-36b275a3b925-00%40eu-central-1.amazonses.com.

Re: [Django] #33256: Some schema tests don't clean up their tables

2022-03-09 Thread Django

#33256: Some schema tests don't clean up their tables
-+-
 Reporter:  Tim Graham   |Owner:  banani720
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mohammad Ali Mehdizadeh):

 Can I work on this ticket please?

-- 
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/0107017f6f7b6fdb-15cc7ae8-fd80-482c-ba47-5203e5a81fb1-00%40eu-central-1.amazonses.com.

Re: [Django] #30801: Improve guidance for making good use of signals.

2022-03-09 Thread Django

#30801: Improve guidance for making good use of signals.
-+-
 Reporter:  Aymeric Augustin |Owner:  Sarah
 Type:   |  Abderemane
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Abderemane):

 * owner:  (none) => Sarah Abderemane
 * status:  new => assigned


Comment:

 Hi there, I would like to give a try on this ticket, but I'm not sure to
 understand what I should do with this part :

 > As far as I can tell, other signals don't have a great alternative. You
 could replace connection_created by a custom database backend but that's a
 lot more work.

 It's to redirect to the part of the documentation where we define custom
 database or something else?

-- 
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/0107017f6f702371-8f1fd53c-96bc-4beb-ad75-584964118ec2-00%40eu-central-1.amazonses.com.

Re: [Django] #33476: Formatting Code with Black

2022-03-09 Thread Django

#33476: Formatting Code with Black
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson ):

 In [changeset:"b1005c0e4029c23f4e718ce0a7afdfa926c095de" b1005c0]:
 {{{
 #!CommitTicketReference repository=""
 revision="b1005c0e4029c23f4e718ce0a7afdfa926c095de"
 Refs #33476 -- Prevented formatting of .py-tpl files with black by pre-
 commit.

 When using `pre-commit run --all-files`, files explicitly passed to
 black are processed even if they don't match the `include` configuration
 option. For some reason, (only) one of the `*.py-tpl` files is picked up
 by pre-commit. We can avoid this by explicitly excluding certain
 patterns of files for the black hook in the pre-commit configuration.
 }}}

-- 
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/0107017f6ef2e073-65993384-331a-4644-98e4-29e56074fa68-00%40eu-central-1.amazonses.com.

Re: [Django] #33476: Formatting Code with Black

2022-03-09 Thread Django

#33476: Formatting Code with Black
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson ):

 In [changeset:"fa948980341b43e76140ac78dcff30bf0bd65369" fa948980]:
 {{{
 #!CommitTicketReference repository=""
 revision="fa948980341b43e76140ac78dcff30bf0bd65369"
 Refs #33476 -- Used black's force-exclude instead of extend-exclude.

 When using `pre-commit run --all-files`, because the filename is passed
 explicitly, the file referred to in `extend-exclude` is not properly
 excluded. Use `force-exclude` instead to say we really mean it.

 See https://github.com/psf/black/issues/438.
 }}}

-- 
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/0107017f6ef2e041-7464ef27-92e5-431c-adc8-1db8ec2ae104-00%40eu-central-1.amazonses.com.

Re: [Django] #33567: Builtin csrf_failure() view uses wrong charset

2022-03-09 Thread Django

#33567: Builtin csrf_failure() view uses wrong charset
-+-
 Reporter:  MrVichr  |Owner:  Claude Paroz
 Type:  Bug  |   Status:  closed
Component:  CSRF |  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  csrf | Triage Stage:  Ready for checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carlton Gibson ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"93803a1b5f4a08eb064b4cc8b3834ff323be4065" 93803a1]:
 {{{
 #!CommitTicketReference repository=""
 revision="93803a1b5f4a08eb064b4cc8b3834ff323be4065"
 Fixed #33567 -- Avoided setting default text/html content type on
 responses.
 }}}

-- 
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/0107017f6ef2997f-63f7edef-f64a-4d84-8ed3-fe089f5dc98c-00%40eu-central-1.amazonses.com.

Re: [Django] #33569: Add support for multiple values for the x-forwarded-proto header

2022-03-09 Thread Django

#33569: Add support for multiple values for the x-forwarded-proto header
-+-
 Reporter:  Thomas Schmidt   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 [https://github.com/django/django/pull/15488 PR]

-- 
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/0107017f6eb1a8ce-6c81c52a-2288-4caa-9e32-9409fbc29841-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2022-03-09 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by John Speno):

 * cc: John Speno (added)


-- 
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/0107017f6e58840e-9983b432-b0ac-457d-b0a4-81f63ddd47eb-00%40eu-central-1.amazonses.com.

Re: [Django] #33567: Builtin csrf_failure() view uses wrong charset

2022-03-09 Thread Django

#33567: Builtin csrf_failure() view uses wrong charset
-+-
 Reporter:  MrVichr  |Owner:  Claude Paroz
 Type:  Bug  |   Status:  assigned
Component:  CSRF |  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  csrf | Triage Stage:  Ready for checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


-- 
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/0107017f6e07545b-c51fd6b7-b02d-4b8d-a3a5-470f8c0b9f6b-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2022-03-09 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by raydeal):

 * cc: raydeal (added)


-- 
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/0107017f6dfef227-5eacb681-132c-4c4e-98c0-a140c39f4d54-00%40eu-central-1.amazonses.com.

Re: [Django] #33567: Builtin csrf_failure() view uses wrong charset

2022-03-09 Thread Django

#33567: Builtin csrf_failure() view uses wrong charset
-+
 Reporter:  MrVichr  |Owner:  Claude Paroz
 Type:  Bug  |   Status:  assigned
Component:  CSRF |  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  csrf | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Carlton Gibson):

 * owner:  nobody => Claude Paroz
 * status:  new => assigned


-- 
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/0107017f6df812a7-d0999673-813f-4bac-b95f-d3303c1c83b3-00%40eu-central-1.amazonses.com.

Re: [Django] #33567: Builtin csrf_failure() view uses wrong charset

2022-03-09 Thread Django

#33567: Builtin csrf_failure() view uses wrong charset
-+
 Reporter:  MrVichr  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  CSRF |  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  csrf | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Carlton Gibson):

 * status:  closed => new
 * has_patch:  0 => 1
 * resolution:  needsinfo =>
 * stage:  Unreviewed => Accepted


Comment:

 Good link!

 > It is very important to always label Web documents explicitly. HTTP 1.1
 says that the default charset is ISO-8859-1. ...

 So we can presume the doc is interpreted as ISO-8859-1, rather than UTF-8,
 and so an error (although exact example...)

 {{{
 >>> r = HttpResponse("Hello ", content_type="text/html")
 >>> r.charset
 'utf-8'
 >>> r.serialize_headers()
 b'Content-Type: text/html'

 >>> r = HttpResponse("Hello ")
 >>> r.serialize_headers()
 b'Content-Type: text/html; charset=utf-8'
 }}}

 Claude's, of removing the half-specified `content_type` automatically
 picks up MrVichr's idea to add the explicit `charset`.

-- 
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/0107017f6df7c58a-f4fc51b1-f279-42ca-915a-d6ca23b1f564-00%40eu-central-1.amazonses.com.

Re: [Django] #33569: Add support for multiple values for the x-forwarded-proto header

Re: [Django] #31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method.

Re: [Django] #33569: Add support for multiple values for the x-forwarded-proto header

Re: [Django] #30923: Out of date examples in docs that call render() with a Context instance instead of regular dict

Re: [Django] #32604: File uploads larger than FILE_UPLOAD_MAX_MEMORY_SIZE get wrong unix group based on setgid

Re: [Django] #30923: Out of date examples in docs that call render() with a Context instance instead of regular dict

Re: [Django] #33256: Some schema tests don't clean up their tables

Re: [Django] #30801: Improve guidance for making good use of signals.

Re: [Django] #33476: Formatting Code with Black

Re: [Django] #33476: Formatting Code with Black

Re: [Django] #33567: Builtin csrf_failure() view uses wrong charset

Re: [Django] #33569: Add support for multiple values for the x-forwarded-proto header

Re: [Django] #21961: Add support for database-level cascading options

Re: [Django] #33567: Builtin csrf_failure() view uses wrong charset

Re: [Django] #21961: Add support for database-level cascading options

Re: [Django] #33567: Builtin csrf_failure() view uses wrong charset

Re: [Django] #33567: Builtin csrf_failure() view uses wrong charset

17 matches

Site Navigation

Mail list logo

Footer information