Timeline for API Endpoint Changes Coming In Version 2.0
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 18, 2020 at 8:33 | history | edited | CommunityBot |
Commonmark migration
|
|
| Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://stackapps.com/ with https://stackapps.com/
|
|
| Dec 11, 2011 at 4:00 | answer | added | Eric Bloch | timeline score: 0 | |
| Dec 1, 2011 at 0:17 | comment | added | Eric Bloch | I was disappointed to hear about the limit to wildcard certs. This site digicert.com/welcome/wildcard-plus.htm proports to sell certs that will work for foo.bar.example.com and bar.example.com - Their copy says: Even more, DigiCert WildCard ssl certificates are unique in allowing you to secure ANY subdomain of your domain, including multiple levels of subdomains with one certificate. For example, your WildCard for *.digicert.com com could include server1.sub.mail.digicert.com as a subject alternate name. | |
| Oct 15, 2011 at 15:58 | comment | added | Jonathan. | @KevinMontrose, I see the point about simplifying it. I have read lots about "problems" where there is more than one site on a server, having different certificates for multiple sites on one IP. Surely stack exchange is the opposite of that problem? | |
| Oct 15, 2011 at 15:34 | comment | added | Kevin Montrose |
@Jonathan - eh, once we're changing domain naming schemes I'd rather simplify. It'd also be pretty weird to make api. anything but the lowest subdomain, can't think of anyone who does differently. That'd also still be a lot of certs, *.stackexchange.com, *.api.stackexchange.com, *.meta.api.stackexchange.com, and then equivalents for SO, SU, SF, Stack Apps, Ask Ubuntu, and *.stackauth.com. Schemes 2, 3, & 4 get us down to two, *.stackexchange.com and *.stackauth.com.
|
|
| Oct 15, 2011 at 10:05 | comment | added | Jonathan. | @KevinMontrose you could change the api URL to math.api.stackexchange, and math.meta.api.stackexchange.com. So kind of like option 3 & 4 but without the site in the query string or path. | |
| Oct 15, 2011 at 0:34 | comment | added | Marco Ceppi |
@KevinMontrose Good point, I forgot it was api.
|
|
| Oct 15, 2011 at 0:27 | comment | added | Kevin Montrose |
@Marco - wildcards certs don't descend beyond one level. *.stackexchange.com matches math.stackexchange.com but not api.math.stackexchange.com or api.meta.math.stackexchange.com. It's kind of a crock IMO, but that's the way they work.
|
|
| Oct 14, 2011 at 22:08 | comment | added | Marco Ceppi | You only have a handful of unique URLS: stackoverflow.com, stackexchange.com, superuser.com, serverfault.com, stackauth.com, askubuntu.com - Surely you would just get a wildcard SSL cert for stackexchange.com then individual certs for those that have top level domains. | |
| Oct 14, 2011 at 22:04 | answer | added | Nathan Osman | timeline score: 4 | |
| Oct 14, 2011 at 20:59 | comment | added | Jonathan. | @Kevin, isn't it possible to get a certificate that covers more than one domain? | |
| Oct 14, 2011 at 20:58 | comment | added | Jonathan. | @Kevin, at least take off the .com, having dots in the middle of an url doesn't sound that normal? | |
| Oct 14, 2011 at 20:31 | comment | added | Kevin Montrose | @ThomasMcDonald - ah, sorry I misunderstood. I'll think on that, probably not a bad idea. | |
| Oct 14, 2011 at 20:30 | comment | added | nobody |
Well, I was referring more to knocking the *.stackexchange.com off the end and using the remainder instead.
|
|
| Oct 14, 2011 at 20:28 | comment | added | Kevin Montrose | @ThomasMcDonald - not for on the fly querying, unless you know that StackApps is id 101 off hand. | |
| Oct 14, 2011 at 20:25 | comment | added | nobody |
Would it not be better to use a unique ID for each site, rather than the domain? apple, gaming, wordpress etc?
|
|
| Oct 14, 2011 at 19:03 | history | asked | Kevin Montrose | CC BY-SA 3.0 |