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

Add support for custom headers #446

Closed
fool opened this issue Apr 22, 2019 · 4 comments · Fixed by #754
Closed

Add support for custom headers #446

fool opened this issue Apr 22, 2019 · 4 comments · Fixed by #754
Labels

Comments

@fool
Copy link
Contributor

fool commented Apr 22, 2019

- Do you want to request a feature or report a bug?

feature

- What is the current behavior?

netlify custom headers (cf https://www.netlify.com/docs/headers-and-basic-auth/#custom-headers) are not supported

- If the current behavior is a bug, please provide the steps to reproduce.

attempt to use a custom header from a dev instance, do not see the expected value

- What is the expected behavior?

attempting to use a path covered by a header from a dev instance should return contents with that custom header

- Please mention your node.js, and operating system version.

all

@Illyism
Copy link

Illyism commented May 8, 2019

Would be nice to test your headers setup, such as Content-Security-Policy before deploy

@overlordofmu
Copy link

@kennedyrose
Copy link

Would absolutely love to see this. We have to pass headers to hit up our internal APIs and without this it's impossible to test before deploying.

@RaeesBhatti RaeesBhatti transferred this issue from netlify/netlify-dev-plugin Aug 12, 2019
@MichalStaruch
Copy link

Honoring headers like CSP defined in _headers file would be a great feature to see in netlify dev. Without that development pipeline loses a lot of consistency. Site that looks good on localhost may be a total mess when deployed on production (strict CSP won't allow inline JS and CSS to run, for example).

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

Successfully merging a pull request may close this issue.

6 participants