Opened 7 years ago
Last modified 5 years ago
#17574 assigned enhancement
Dojo XMLHttpRequest.withCredentials support
Reported by: | ishenkoyv | Owned by: | dylan |
---|---|---|---|
Priority: | undecided | Milestone: | 1.15 |
Component: | IO | Version: | 1.9.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
I'm building REST API server with role based subdomains, e.g. api.admin.example.com, api.client.example.com. REST API authentication server currenly supports only 2 ways to authenticate - session based authentication for example.com and http basic authentication. That's why I want to use CORS requests with withCredentials. There is related closed ticket to add withCredentials support to dojo https://bugs.dojotoolkit.org/ticket/11820 and 1.9.1 already has it. But I don't see any information about browsers support. In tests I can see some notes like
Note: this isn't really testing much unless you are using IE8 (XDomainRequest)
. There are also discussions on stackoverflow like this http://stackoverflow.com/questions/14587347/dojo-cross-domain-access-is-denied. Does dojo fully supports withCredentials including IE8, IE9, IE10? Or what broswers are supported?
Another question. From http://dojotoolkit.org/reference-guide/1.9/dojo/store.html
The following two core stores based on the typical pattern of in-memory and server-based data stores: dojo/store/Memory ... dojo/store/JsonRest
How can I use JsonRest? with CORS withCredentials if I can't pass withCredentials option to request?
return xhr("GET", { url: this.target + id, handleAs: "json", headers: headers });
Should I implement my own store? I can't find any info about this at http://dojotoolkit.org/
I have tried to ask these questions at dojo IRC but with no answer.
I set ticket type to enhancement
- withCredentials support including IE browsers
- JsonRest? store withCredentials support
Change History (2)
comment:1 Changed 5 years ago by
Milestone: | tbd → 1.12 |
---|---|
Owner: | set to dylan |
Status: | new → assigned |
comment:2 Changed 5 years ago by
Milestone: | 1.13 → 1.15 |
---|
Ticket planning... move current 1.13 tickets out to 1.15 to make it easier to move tickets into the 1.13 milestone.