Support HTTP OPTIONS method

[encode]

Support HTTP OPTIONS method

[markotibold]

What Response header fileds should be implemented for HTTP OPTONS requests?

Allow (GET, HEAD, OPTIONS, PUT, POST, DELETE, )
......
Other HTTP Response header fields

[tomchristie]

Okay, so I'm thinking that most of the information will be in the response body.
Something along these lines:

{
'name': 'MyExample',
'description': 'This is my example resource',
'fields': {'foo': 'IntegerField', 'bar': 'CharField'}
'renders': ['application/json', 'application/xml'],
'parses': ['application/json', 'application/xml']
}

And possibly some other information (perhaps even listing the permissions.)
In terms of header fields I really can't think of anything other than the standard 'Allow'.

The acid test of if the OPTIONS support is good enough might be if someone would be able to implement the browse-able API using a 3rd party AJAX client.

[tomchristie]

See discussion on the list: https://groups.google.com/d/topic/django-rest-framework/Eap5nELLt1I/discussion

[tomchristie]

Done.