Camarellini Viberg
Reputation: 303
What is the benefit of manually specifying the MIME type when sending an AJAX request?
The jQuery library has a built in function called .overrideMimeType(). Why is this a beneficial thing to do? What kind of issues may arise if I don't do this? It seems to crop up quite frequently, but I can't find a good explanation via Google.
Thank you for your help.
Upvotes: 0
Views: 45
Answers (1)
Quentin
Reputation: 944564
It hacks around web services which lie about what sort of content they are serving.
Most commonly, this involves PHP scripts since PHP defaults to claiming Content-Type: text/html and many PHP authors don't know they should header("Content-Type: application/json"); before they echo json_encode($some_data);.
Upvotes: 2
Related Questions
- When to use the JavaScript MIME type application/javascript instead of text/javascript?
- What do browsers want for the Content-Type header on json ajax responses?
- Why write <script type="text/javascript"> when the mime type is set by the server?
- Request's content-type header contains more than the MIME type, why?
- why do I need to include enctype="multipart/form-data" when sending data through form but don't need when sending through xmlhttprequest
- Is explicitly setting the contentType for jQuery ajax necessary when posting JSON?
- Is it important to state a MIME type when including a JS file?
- Why are mime types not usually set correctly?
- MIME versus JSON for HTTP POST body
- What is the importance of correct MIME types?