Last modified: 2014-04-04 18:43:56 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 27946 - (ssl) SSL related (tracking)
(ssl)
SSL related (tracking)
Status: NEW
Product: Wikimedia
Classification: Unclassified
SSL related (Other open bugs)
unspecified
All All
: Normal enhancement with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: tracking
Depends on: 29008 31323 31327 33890 39676 47832 48133 51002 53526 53636 225 5440 16302 16822 18496 19429 19587 20454 20643 21514 22982 23559 24332 25271 26971 27448 27622 27909 27912 27968 29014 29410 29878 29898 29977 29981 30294 30329 30560 31333 31334 31335 31369 31437 31531 31539 31563 32769 36456 39380 45765 47276 48402 49698 52949 53379 58292
Blocks: tracking 41022
  Show dependency treegraph
 
Reported: 2011-03-08 23:58 UTC by p858snake
Modified: 2014-04-04 18:43 UTC (History)
11 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description p858snake 2011-03-08 23:58:30 UTC
Tracking for secure server issues.
Comment 1 Alex Monk 2013-04-26 19:20:17 UTC
Should this be resolved now that the secure server is deprecated, everything turned into redirects to the proper domains, etc.?
Comment 2 Andre Klapper 2013-04-29 08:33:47 UTC
"secure server issues" description is vague (in case that it was meant to only refer to https://secure.*), so this report now also has issues about SSL and https:// on *any* servers.

p858snake: Please clarify.
Comment 3 p858snake 2013-04-29 08:43:16 UTC
Yes, Previously it was based on the "secure" cluster before it was deprecated and replaced with the current setup, But based on the current list of open depends it's quiet clear that this bug has easily evolved it self to handle the current system.

I'm not sure why anyone would consider closing a tracking bug with approx. 10 open bugs attached
Comment 4 Alex Monk 2013-04-29 15:44:00 UTC
(In reply to comment #3)
> I'm not sure why anyone would consider closing a tracking bug with approx. 10
> open bugs attached

We have an "SSL related" component which I think is better than a tracking bug.
Comment 5 p858snake 2013-04-29 22:01:28 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > I'm not sure why anyone would consider closing a tracking bug with approx. 10
> > open bugs attached
> 
> We have an "SSL related" component which I think is better than a tracking
> bug.

Which, If you have looked they aren't all in.
Comment 6 Nemo 2014-04-03 09:38:14 UTC
Bug 33890 comment 26 has some medium-term information by Faidon ("There is going to be most likely a quarterly SSL/SPDY goal").

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links