Side navigation
#13893 closed bug (duplicate)
Opened May 14, 2013 12:21PM UTC
Closed May 14, 2013 04:02PM UTC
Last modified May 15, 2013 07:36AM UTC
SSL Certificate for code.jquery.com is incorrect
| Reported by: | martijn@thany.nl | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | unfiled | Version: | |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
The SSL certificate for code.jquery.com is incorrect. This makes it impossible to include jquery from this CDN on a secured website, because the browser will not load jquery by default.
Go to https://code.jquery.com/ to see what I mean.
If it *shouldn't* work, then the server should not respond on this URL at all. I hope it *should* work, in which case the certificate needs to be updated.
Attachments (0)
Change History (6)
Changed May 14, 2013 04:02PM UTC by comment:1
| resolution: | → duplicate |
|---|---|
| status: | new → closed |
Changed May 14, 2013 04:22PM UTC by comment:2
I understand, but then the server should not respond on this url. No matter how you put it, it's something that's not right...
Changed May 14, 2013 04:27PM UTC by comment:3
To clarify - the server is trying to respond with an incorrect certificate. So it does support SSL, it's just not configured correctly.
If the server isn't *supposed* to support SSL, then it should respond with no certificate, or return a proper error, or not return anything, or something else that doesn't produce a confusing error.
Changed May 14, 2013 04:35PM UTC by comment:4
We're working on this. But this is not the appropriate place to repot a problem with the CDN, hence the other ticket being closed as not a bug.
Changed May 14, 2013 04:45PM UTC by comment:5
Clearly it's easy and cheap to fix on your end. On our end it's not a single server but actually an entire CDN taking requests from a large number of sites. If it were just the cost of a cert we could easily add one, but the CDN provider charges more for HTTPS access than for standard access.
We're looking to see if we can get someone to sponsor HTTPS access on our CDN, which is likely to run several thousands of dollars per month, so that you can enjoy such access without spending money or using your own server resources. In the meantime, please use another CDN or host the file locally.
Changed May 15, 2013 07:36AM UTC by comment:6
I understand, and thanks for explaining.
But I have to say, the server should then not respond on HTTPS at all, should it?
Duplicate of #13322.We encourage the use of the Google CDN if SSL is needed.