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

Implement HTTPS for Trac Pages #5214

Closed
nvaccessAuto opened this issue Jul 13, 2015 · 2 comments
Closed

Implement HTTPS for Trac Pages #5214

nvaccessAuto opened this issue Jul 13, 2015 · 2 comments

Comments

@nvaccessAuto
Copy link

Reported by elliott94 on 2015-07-13 07:28
Lots of websites are now modifying their web server config to serve an encrypted version of a website by default. This has two major advantages; search engines including Google have previously explained that sites secured using HTTPS will be displayed before those that don't, which in theory could offer further exposure to the project as a whole. Furthermore, when a user enters their username/password to login to Trac this information is currently sent unencrypted, which presents the possibility of interception (on an unsecured 802.11 network, for example). Is this something that you would consider adding to the website?

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2015-07-13 07:35
If we stay with Trac, we might consider doing it for authenticated users (or at least for the authentication process). However, there's no good reason to do this for unauthenticated users, since there's nothing to secure, so the only thing we'd gain is increased server load. The search engine prioritisation thing isn't sufficient IMO; I didn't even know about this before now. Regardless, this is not likely to happen in the near-term.

It's worth noting that we're considering moving everything to GitHub or similar, which would make this irrelevant.

@jcsteh
Copy link
Contributor

jcsteh commented Mar 9, 2016

We're on GitHub now (which uses https), so this is done.

@jcsteh jcsteh closed this as completed Mar 9, 2016
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

2 participants