Re: New feature: HTTP OPTIONS and improved HEAD for View

2011-12-22 Thread Steven Cummings
Created a ticket with the patch: https://code.djangoproject.com/ticket/17449 -- Steven On Sun, Dec 11, 2011 at 3:29 PM, Steven Cummings wrote: > I'll probably go ahead and log it and start the patch soon. Your feedback > on truncation for HTTP HEAD was helpful, and the rest doesn't seem very > c

Re: New feature: HTTP OPTIONS and improved HEAD for View

2011-12-11 Thread Steven Cummings
I'll probably go ahead and log it and start the patch soon. Your feedback on truncation for HTTP HEAD was helpful, and the rest doesn't seem very controversial. -- Steven On Sat, Dec 10, 2011 at 5:26 AM, Jamie Matthews wrote: > Just bumping this - can anyone suggest what the next steps should be

Re: New feature: HTTP OPTIONS and improved HEAD for View

2011-12-10 Thread Jamie Matthews
Just bumping this - can anyone suggest what the next steps should be? It'd be nice to get it fixed for 1.4. Thanks, Jamie On Nov 28, 5:59 pm, Jamie Matthews wrote: > > Yeah, that implementation seems preferable. What was the reason for backing > > it out? > > Not sure. What would be the procedu

Re: New feature: HTTP OPTIONS and improved HEAD for View

2011-11-28 Thread Steven Cummings
I assumed I needed the votes here to get going on that. In the past when I've started with a ticket I've been directed here to gather support first. -- Steven On Mon, Nov 28, 2011 at 11:59 AM, Jamie Matthews wrote: > > Yeah, that implementation seems preferable. What was the reason for > backing

Re: New feature: HTTP OPTIONS and improved HEAD for View

2011-11-28 Thread Jamie Matthews
> Yeah, that implementation seems preferable. What was the reason for backing > it out? Not sure. What would be the procedure for getting this changed? Open a new ticket, I assume? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to

Re: New feature: HTTP OPTIONS and improved HEAD for View

2011-11-27 Thread Steven Cummings
On Sun, Nov 27, 2011 at 4:17 PM, Jamie Matthews wrote: > > 2. Improve the default HTTP HEAD handler by ensuring it has a blank body, > > as this is the expectation of a response to a HEAD request. Also, there > > should be consideration for the GET handler not existing, which should > > result in

Re: New feature: HTTP OPTIONS and improved HEAD for View

2011-11-27 Thread Jamie Matthews
> 2. Improve the default HTTP HEAD handler by ensuring it has a blank body, > as this is the expectation of a response to a HEAD request. Also, there > should be consideration for the GET handler not existing, which should > result in a 405. The code appears to assume it exists, which would result