The name says it all.
Project description
DRF URL Content Type Override
DRF URL Content Type Override allows the content type of the request to be overriden with a url parameter.
Why would I need this?
Sometimes it makes sense to override the content type specified in the header. For example, some browser’s XHR, such as IE9, are unable to support CORS. Pollyfills like, jQuery-ajaxTransport-XDomainRequest or httpplease’s oldiexdomain.js plug-in get around this by using XDomainRequest, which supports CORS. The problem is XDomainRequest only sends a content type of text/plain in the header. This is problematic when POSTing form data. DRF URL Content Type Override let’s you specify a content type which will override the header value.
Install
pip install drf-url-content-type-overrideAdd ‘DEFAULT_CONTENT_NEGOTIATION_CLASS’
REST_FRAMEWORK = {
'DEFAULT_CONTENT_NEGOTIATION_CLASS': 'drf_url_content_type_override.URLOverrideContentNegotiation',
}Usage
Example: Javascript on a different domain from the API.
jquery.ajax({
'url': 'http://apidomain.com/api/1/contact?_content_type=application/x-www-form-urlencoded',
'type': 'POST',
'data': {'name': 'Chris'}
})For more background see https://github.com/tomchristie/django-rest-framework/pull/1731
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Hashes for drf-url-content-type-override-1.0.0.tar.gz
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | a95acba1690587180205454f5b3d8a15613cec64b51c8e507c3cbdc06d47f701 |
|
| MD5 | 942f87b09c96c188f8e8fc109507a70b |
|
| BLAKE2b-256 | e33f1045c170917032fda04cfdbb47a02749baf59b1714d4e9db6c13978b9f2c |
