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.

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

Remove all Google Chrome Frame related config #154

Closed
wants to merge 9 commits into from
Closed

Remove all Google Chrome Frame related config #154

wants to merge 9 commits into from

Conversation

Rowno
Copy link
Contributor

@Rowno Rowno commented Jun 18, 2013

alrra and others added 8 commits April 2, 2013 00:34
@alrra
[iis] Change font/otf → font/opentype
b3f5803 
References: h5bp/html5-boilerplate#1317
@alrra
[nginx] Remove text/html from gzip_types
bccd592 
Fix: #144.
@alrra
[apache] Update docs on required modules
bb8fbd6
@alrra
Update README.md
17152fc
@mattbrundage @alrra
[apache] More elegant way of matching svg/svgz
561c376
@Ekman @alrra
[lighttpd] Security enhancements
22f0214 
- Avoid revealing the server name and version number
- Disable directory listing

Ref: #150
@alrra
[apache] Add includeSubDomains directive to HSTS
f25e498 
The `includeSubDomains` optional directive allows the user to apply the
`HTTP Strict Transport Security` rule to all of the site's subdomains:
* http://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-14#section-6.1
* https://developer.mozilla.org/en-US/docs/Security/HTTP_Strict_Transport_Security

Ref: #151
@rwblackburn @alrra
[apache] Fix rewrite rule conditions for localhost
e7ad187 
Add `localhost` and `127.0.0.1` exceptions to the rewrite rule condi-
tions that prepend `www.` to URLs, as the current rules prevent users
from being able to test locally.

Closes #152.
@alrra
Copy link
Member

alrra commented Jun 18, 2013

@Rowno thanks!

Can you also add the "Retiring Chrome Frame" link to the commit message and, if you have time, update the docs to include the Chrome Frame related information (at least for Apache) ?

From: "Retiring Chrome Frame"

Given these factors we’ve decided to retire Chrome Frame, and will cease support and updates for the product in January 2014.

The initial issue was mostly intended as a reminder so, this will have to wait a while till it will get pulled in, sorry.

@Rowno
Copy link
Contributor Author

Rowno commented Jun 18, 2013

I'm not sure what should be added to the docs, so I'll leave that up to you. 😉

@ChrisMcKee
Copy link
Member

IIS/.Net Sections merged.

@alrra
Copy link
Member

alrra commented Jun 27, 2013

IIS/.Net Sections merged.

@ChrisMcKee: I appreciate your quickness, but let's not rush into things. Google Chrome Frame is still officially supported until January 2014, so when we remove it, I think it would be nice to have a tag which still includes the Chrome Frame HTTP header hint (I will come with some proposals on tagging and other repository related things soon).

@ChrisMcKee
Copy link
Member

@alrra fair enough; I'll undoubtedly need to add some new configs soon depending on what they've altered for MVC5/API2.

@alrra
Copy link
Member

alrra commented Jul 29, 2013

@Rowno I'm going to close this in favor of the server specific issues, as some of the server will have to make some other changes first. Thanks anyhow, really appreciate the effort!

@alrra alrra closed this Jul 29, 2013
@wavedocs wavedocs mentioned this pull request Jun 20, 2014
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
apache gae iis lighttpd nginx
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@Rowno @alrra @ChrisMcKee @mattbrundage @Ekman @rwblackburn