Skip to content
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.

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

Assess CORS - Should Aye Aye handle it? #15

Closed
Gisleburt opened this issue Mar 9, 2015 · 1 comment
Closed

Assess CORS - Should Aye Aye handle it? #15

Gisleburt opened this issue Mar 9, 2015 · 1 comment
Assignees
Milestone

Comments

@Gisleburt
Copy link
Member

See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS

@Gisleburt Gisleburt added this to the 1.0.0-beta.4 milestone Mar 9, 2015
@Gisleburt Gisleburt self-assigned this Mar 9, 2015
@Gisleburt Gisleburt changed the title Assess CORS - Should Aye Aye handle it itself? Assess CORS - Should Aye Aye handle it? Mar 9, 2015
@Gisleburt
Copy link
Member Author

AyeAye doesn't prevent CORS you can just create an endpoint to send the correct headers.

/**
 * CORS Access Control information
 */
public function optionsUserEndpoint()
{
    header('Access-Control-Allow-Methods: GET,POST');
    header('Access-Control-Allow-Headers: origin, content-type, accept');
}

It's definitely something that can be imporved, but for the time being I'm closing this off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant