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

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 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