Typo in Headers #5
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Running this out of the box wasn't setting the Content-Type correctly for me in Chrome. Instead of setting "Content-Type," it was just adding a header "Content Type", which had no affect on how the file was processed. My stylesheets were coming in as text/plain. After adding the "-", the header was written correctly, and the browser was able to read my CSS.
|
I dont know if this is actually affecting people or not, but I thought I'd share the fix I had to make! Thanks for the code and the youtube videos! |
|
It doe's effected my test run. I changed from "Content Type" to "Content-Type". Everything is working fine now. :) |
|
This will also need to be merged into branches 07 through 20. |
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Running this out of the box wasn't setting the Content-Type correctly for me in Chrome. Instead of setting "Content-Type," it was just adding a header "Content Type", which had no affect on how the file was processed. My stylesheets were coming in as text/plain. After adding the "-", the header was written correctly, and the browser was able to read my CSS.