1. #1

    CDN -

    Hi Guys, is not available. is..

    Is that on purpose ?


  2. #2
    Hello Martin!

    You are having a strange and unexpected experience with the CDN, I only see this happening if your network is redirecting traffic to GitHub endpoints.

    Here are some techie stuff that might help you and your network team diagnose the issue if it persists on your end.

    Currently if you make an HTTP request (non HTTPS), it will respond with a permanent redirect to HTTPS endpoint, so your result very strange for us.

    I have just checked and I am getting the expected values:

    - HTTP - 301 redirect, invalid resource address
    $ curl -i
    HTTP/1.1 301 Moved Permanently
    - HTTPS - 404 not found, invalid resource address
    $ curl -i
    HTTP/2 404
    - HTTP - 301 redirect, valid resource address
    $ curl -I
    HTTP/1.1 301 Moved Permanently
    - HTTS - 200 found, valid resource address
    $ curl -I
    HTTP/2 200
    Check again, if you still get this error, check from other networks and check with your network if you are having any redirects to GitHub resources.

    Currently, should be resolving, DNS-wise, to the following IP addresses:

    ;; ANSWER SECTION:          98      IN      CNAME       3010    IN      A       3010    IN      A       3010    IN      A       3010    IN      A
    Queries to one of those IP addresses should show the following headers; different headers suggest tampering with your connection:

    $ curl -I
    HTTP/1.1 404 Not Found
    Content-Type: text/html; charset=utf-8
    x-origin-cache: HIT
    ETag: "5f77c9f3-239b"
    Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
    X-GitHub-Request-Id: BD62:29B2:A886C:3AECE1:60706D5E
    Content-Length: 9115
    Accept-Ranges: bytes
    Date: Fri, 09 Apr 2021 15:06:06 GMT
    Via: 1.1 varnish
    Age: 0
    Connection: keep-alive
    X-Served-By: cache-gig17035-GIG
    X-Cache: MISS
    X-Cache-Hits: 0
    X-Timer: S1617980766.200696,VS0,VE116
    Vary: Accept-Encoding
    X-Fastly-Request-ID: eadf4d4a1c52f881c0f800feb9ef190b3348e5ea
    While the output above is correct for current state, this may change without notice in the future, so you should use these headers as base within the next few days but there's no guarantee the HTTP headers will look the same, say, in year 2022 or later.

    Hope this helps!
    Last edited by fabricio.murta; Apr 09, 2021 at 4:10 PM.
  3. #3
    The http URL's will automatically redirect to https.

    The following URL should return a 404. That is the expected result.

    Because, there is nothing at that endpoint.

    If you change to point to a .js file:

    Then it should automatically redirect to https:

    Hope this helps.
    Geoffrey McGill
  4. #4

    Very late reaction

    Hi Guys,

    I forgot this question last year. Thanks for the info !


Similar Threads

  1. Replies: 0
    Last Post: Mar 18, 2017, 2:33 PM
    By RCN in forum 3.x Legacy Premium Help
    Replies: 5
    Last Post: Feb 27, 2015, 5:25 PM
  3. Ext.Net MVC using CDN for static files
    By RandomEugene in forum 2.x Help
    Replies: 0
    Last Post: Jul 02, 2013, 5:30 PM
  4. Replies: 3
    Last Post: Jul 17, 2012, 2:44 PM
  5. [CLOSED] Using CDN for Ext.Net static files
    By jmcantrell in forum 1.x Legacy Premium Help
    Replies: 22
    Last Post: Jul 28, 2011, 8:42 PM

Posting Permissions