Enabling this is trivial, the question is: is there any reason we *can't* enable this? Who's responsible for this service and might know of exceptions like mixed-content, or HTTPS-incapable tools which rely on it, etc? [note this a generic message being tacked into the description of several similar tickets]
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
datasets: rewrite http to https | operations/puppet | production | +6 -0 |
Event Timeline
How does that not redirect already? I thought/hoped that the 'default' parameter in the nginx conf on datasets would take care of that. https://gerrit.wikimedia.org/r/#/c/278861/6/modules/dumps/templates/nginx.dumps.conf.erb Anyways, yes please redirect it all!
Change 283084 had a related patch set uploaded (by Dzahn):
datasets: rewrite http to https
Nope, all the services that do this have a rule in the backend based on RewriteCond %{HTTP:X-Forwarded-Proto} !https
https://gerrit.wikimedia.org/r/#/c/283084/1/modules/statistics/files/datasets.wikimedia.org
Somewhat counterintuitively the config for this is not in module dataset but instead in modules/statistics/files/ and it's not nginx but Apache?
That just can't be true. And yet it is. 2d1fa5938f22c94324435c75acc4f496c1cacaa3 @Ottomata set it up. Someone has to ask him about this, I have zero idea.
Hah, and that says **"# NOTE: This class has nothing to do with the # datasets site hosted at 'datasets.wikimedia.org'." ** ? ?
Change 283084 abandoned by Dzahn:
datasets: rewrite http to https
Reason:
can be done in varnish
datasets.wikimedia.or is hosted on stat1001, not a dataset100x host.
I think HTTPS only is fine, but maybe @Milimetric or @mforns or @Halfak might have more to say.
Change 283207 had a related patch set uploaded (by BBlack):
datasets.wm.o HTTPS redirect T132463
@Ottomata
We might want to change this to https then: https://github.com/wikimedia/analytics-dashiki/blob/master/src/app/config.js#L39