Skip to content

feat(serve): allow CORS access while running ng serve (#2872) #3009

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

Merged
merged 2 commits into from
Nov 11, 2016

Conversation

filoxo
Copy link
Contributor

@filoxo filoxo commented Nov 3, 2016

Fix #2872

@filoxo
Copy link
Contributor Author

filoxo commented Nov 4, 2016

@filipesilva Here's that PR as requested in #2872.

@filipesilva
Copy link
Contributor

Looks good, will merge soon!

@hansl hansl merged commit 7c834a8 into angular:master Nov 11, 2016
MRHarrison pushed a commit to MRHarrison/angular-cli that referenced this pull request Feb 9, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to access assets due to CORS
4 participants