Skip to content

Cross Domain Ajax #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
bmeck opened this issue Jun 14, 2010 · 4 comments
Closed

Cross Domain Ajax #1

bmeck opened this issue Jun 14, 2010 · 4 comments

Comments

@bmeck
Copy link

bmeck commented Jun 14, 2010

honoring the 'access-control-request-method','origin', and other CDR headers could aid a lot of development to work around that.
@felixge
Copy link
Collaborator

felixge commented Jun 15, 2010

I don't need this feature, nor does it seem to be defined in an accepted standard at this time.

That being said, I would probably accept a patch for it.

@bmeck
Copy link
Author

bmeck commented Jun 15, 2010

The spec is at. Will look into providing a patch later.
http://www.w3.org/TR/cors/

@felixge
Copy link
Collaborator

felixge commented Jun 15, 2010

Well, it seems to be a draft currently. What browsers are supporting it at this point (besides Firefox)?

@bmeck
Copy link
Author

bmeck commented Jun 15, 2010

(Internet Explorer 8+, Firefox 3.5+, Safari 4+, and Chrome)
http://www.nczonline.net/blog/2010/05/25/cross-domain-ajax-with-cross-origin-resource-sharing/

svnlto pushed a commit that referenced this issue Jan 15, 2013
@mikefrey
Merge pull request #1 from carlos8f/json_parser_2
9bbfe66 
Add test and avoid parse exception
kapouer pushed a commit to kapouer/node-formidable that referenced this issue Oct 9, 2013
@andrewrk
fix hash workaround. closes node-formidable#1
c586a50
kapouer pushed a commit to kapouer/node-formidable that referenced this issue Oct 9, 2013
@andrewrk
Revert "fix hash workaround. closes node-formidable#1"
ae423c7 
This reverts commit c586a50.

Oh right. We need this to support 0.8. When we drop 0.8 support we
can reinstate this change.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@felixge @bmeck