Closed arcfide closed 4 years ago
Just stumbled on the following paragraph:
“For read-only access, instead of CORS, a web service may support the JSONP (JSON with padding) technique. Built-in DevExtreme, Data Store classes support JSONP…”
Link: https://js.devexpress.com/Documentation/Guide/Data_Layer/Data_Source_Examples/#Note_On_Same-Origin_Policy (at the very bottom)
Is JSONP related to what you are doing at the moment?
Best, Alexey
From: Aaron W. Hsu [mailto:notifications@github.com] Sent: Sunday, February 16, 2020 1:32 PM To: Dyalog/Jarvis Jarvis@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [Dyalog/Jarvis] A number of fixes and enhancements (#8)
This pull request does a few things:
You can view, comment on, or merge this pull request online at:
https://github.com/Dyalog/Jarvis/pull/8
Commit Summary
File Changes
Patch Links:
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/Dyalog/Jarvis/pull/8?email_source=notifications&email_token=AFAAUMQWDDT7J4AW3OYU3JLRDEI2HA5CNFSM4KWB2SIKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IN2WKAQ, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFAAUMQYN5J5SOWOORIVN23RDEI2HANCNFSM4KWB2SIA.
@aim1956 This PR does not deal with JSONP at all, and was an initial part of a rework on my part to enable easy CORS support on my side. I am working with Brian to integrate automatic CORS handling into Jarvis. Hopefully we'll have something come of that.
This pull request does a few things:
DefaultContentType
to only use it when dealing with REST handling where another content type has not been provided. This prevents this setting from interfering with JSON handling and other important types, as well as with interfering with good responses for CORS handling.