NOTICE: SockJS CDN will be retired on 1 Dec 2014 #198
Comments
|
@brycekahle might be smart to release a version in the CDN which simply adds a console.log message stating that the CDN will be retired with a reference to this issue. |
|
@3rd-Eden That sounds like a good idea. Thanks. |
|
I quite like having the CDN option. Currently a SockJS server requires 0 configuration. Without it a SockJS URL would have to be configured, e.g. for the iframe_htmlfile transport, which is needed with Java servers (for the jsessionid cookie). Not a big deal but a very convenient default. |
|
@rstoyanchev We can easily switch the default to one of the CDNs listed above. It is quite expensive to have a custom CDN just for this. |
|
Right, I see. Are you actually pulling the plug in 2 weeks? We'll update the Spring Framework and fortunately we have releases next week but not everyone will upgrade within 2 weeks. A little extra time would go pretty far in causing the least disruption. |
|
How much more time do you need? |
|
@rstoyanchev We will try to keep cdn.sockjs.org running at least to 1st Dec. |
|
sounds good thanks. |
This commit updates the default location of the SockJS' client library. The previous location is being retired by the project maintainers. The new default location is backed by several CDN providers: * https://cdn.jsdelivr.net/sockjs/0.3.4/sockjs.min.js See sockjs/sockjs-client#198 Issue: SPR-12254
This commit updates the default location of the SockJS' client library. The previous location is being retired by the project maintainers. The new default location is backed by several CDN providers: * https://cdn.jsdelivr.net/sockjs/0.3.4/sockjs.min.js See sockjs/sockjs-client#198 Issue: SPR-12254 (cherry picked from commit a6e1c53)
|
Warning added to CDN hosted versions for 0.3 (alias to 0.3.4), 0.3.2, and 0.3.4. |
brycekahle
changed the title
|
I assume this effects the websocket multiplex JS as well since it is also hosted in the same CDN server? In fact I am already getting a 403 for that file. What is the new CDN to use for that file? |
|
@ryanjbaxter I've posted the file in the releases. It is probably best if you host it yourself. I can see about getting that on jsDelivr if you like. |
@brycekahle: It seems cdn.jsdelivr.net is listed on hosts-file.net as an "Ad/tracking server" and is therefore blocked by default by µMatrix. |
|
Going to contact them to change the classification. |
|
@BrunoQC cdn.jsdelivr.net was removed and got white-listed, meaning it wont happen again. |
|
@jimaek No problem. Thanks for the quick fix 👍 |
* Fixes the [deprecated](sockjs/sockjs-client#198) URL * Lets the browser decice if http or https is used
This is a public notice that the SockJS CDN (cdn.sockjs.org) will be retired once SockJS v1.0 is released. The release date is currently unknown, but it will be at least later than Oct 9 2014 (2 weeks from today). You are advised to transition as soon as possible.
SockJS is currently available on the following public CDNs:
v1.0 will NOT be available on the SockJS CDN.
Discuss.
The text was updated successfully, but these errors were encountered: