#14955: URLField validation should use HEAD requet instead of GET -------------------------------------+------------------------------------- Reporter: claudep | Owner: jezdez Type: | Status: closed Uncategorized | Component: Core (Other) Milestone: 1.3 | Severity: Normal Version: SVN | Keywords: Resolution: fixed | Has patch: 1 Triage Stage: Ready for | Needs tests: 0 checkin | Easy pickings: 0 Needs documentation: 0 | Patch needs improvement: 0 | UI/UX: 0 | -------------------------------------+------------------------------------- Changes (by jamstooks <ben.stookey@…>):
* ui_ux: => 0 * type: => Uncategorized * severity: => Normal * easy: => 0 Comment: After thinking about this, I wonder if it's worth falling back to GET for any failed request? I've found a variety of IIS servers running ASP.NET that are responding with 403 errors or simply timing out on HEAD requests. Any thoughts? Should I open another ticket about this? -- Ticket URL: <https://code.djangoproject.com/ticket/14955#comment:11> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.