A small issue in this proposition: sub-subdomains are not currently
covered by the https certificate.
~s
Le Thu, 28 Mar 2013 08:41:41 +0100, Petr Bena <benap...@gmail.com> a écrit:
What about inserting another domain just to prevent confusion and to
keep current redirects, which would ONLY allow api, such as
commons.api.wikipedia.org
the *.api.<project> would just be some kind of universal api gateway
for all domains
On Wed, Mar 27, 2013 at 10:07 PM, Juliusz Gonera <jgon...@wikimedia.org>
wrote:
On Fri, Mar 22, 2013 at 9:22 PM, MZMcBride <z...@mzmcbride.com> wrote:
Please draft an RFC at <https://www.mediawiki.org/wiki/RFC>. :-)
http://www.mediawiki.org/wiki/Requests_for_comment/Alternative_Commons_Domains
Please share your comments.
commons.wikipedia.org already redirects to commons.wikimedia.org (for
historical reasons, maybe), so that has to be considered.
Yes, it redirects. But to solve the problem I'm describing, the API
would
need to be served from commons.wikipedia.org.
I think what
you're proposing is also kind of confusing and I'm wondering if there
aren't better ways to approach the problem.
I'm open to suggestions, but I'd rather not wait until CentralAuth gets
completely redesigned and rewritten.
--
Juliusz
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
