About the author

Related Articles

9 Comments

  1. 1
    Ulflander@email.null'

    Ulflander

    In case you have your own domain that point at the CDN (I know CloudFront let you do that), you could use CloudFlare ( https://www.cloudflare.com/ ) as a reverse proxy between your users and the CDN.

    Thanks to their free plan, you can create a rule that redirects everything to index.html. I think this is the only way to achieve what you want, given that CDNs are configured to serve only static existing files as you know.

    Reply
  2. 2
    Sebastien

    Sebastien Lorber

    This guy had a similar problem and used S3 / CloudFront. All his urls redirect to index.html with a statuscode 200.

    This is a workaround as it involves setting index.html as an error page.

    See details: https://kkob.us/2015/11/24/hosting-a-single-page-app-on-s3-with-proper-urls/

    Reply
  3. 3
    Leonidaz@email.null'

    Leonidaz

    I’m in the same boat as you are and it seems that the cdn’s are not supporting url rewriting. The following solution does not solve our “problem” exactly but comes very close to saving $ for hosting if you’re using a “pull” CDN provider.

    Initial load of the default page (index.html) will provide just a tiny piece of the html, basically the bare-bones html structure, like so:

    <!doctype html>
    <html lang="en">
    <head>
        <title>something</title>
        <!-- Load the script "js/main.js" as our entry point -->
        <script data-main="js/main" src="http://mycdn.com/js/libs/require/require.js"></script>
    </head>
    <body>
    
    </body>
    </html>
    

    The rest of the code would be loaded via some (async) module loader like require.js — and all of that code would come from your CDN, including require.js.

    However, even this tiny bit of html in no time will also come from the CDN if you’re using pull CDN. The CDN “pull” provider will hit this page whenever it does not find a file for an html5 pushstate url in its cache.

    On your server you have to have some kind of routing to route every request that matches a pattern where a file extension is not provided from the CDN to this one file.

    Yes, the CDN will hit the site every time a new url is encountered (if you’re using pull CDN) but after it gets it, it will distribute it to all the users from its cache and will not hit your site for the same url again. Also, the hit on your site from the CDN provider will be insignificant since you’re serving a tiny bit of static html. And, if you set your file headers to never expire on this html file (this file should really never change) the file can be kept by the CDN provider for a very long time (depending on the provider), so the hits on your server would pretty much come down to a one time event per a unique url.

    Reply
  4. 4
    David@email.null'

    David

    If you’re considering SEO and friendly URLs, you can accomplish some of that using pushState, sure. Just remember that:

    • When redirecting all routes to index.html you will also serve the exact same html content to the search engines no matter what URL they march in on. Then it wont matter how “SEO-friendly” your URL is.

    • If you’re thinking IE support, it doesn’t support the History API, so you’ll need a higher-level history framework or some other workaround for IE. And that will most likely include #-based URLs. So you will basically have two different URLs for each view, that’s something to consider when people share URLs or figuring out how search robots catches links to your site.

    I would suggest considering the following two options before you go too far in finding a suitable cloud host:

    1. Off-load some of the data logic to the backend and serve at least some digestable content for each view. You can still remove or maybe parse that content in your app and do your pushstate/jsonAPI thing for better UX, but you will have “true”, scannable URLs for the search engines, opera mini users and some other unfortunate browsers. These static pages do not have to serve the same functionality or even styles, just think of it as the last fallback.

    2. Forget about the CDN for the app, just use the CDN for static files, images, scripts etc. You can have a couple of fallbacks for the app itself, but it’s the media that really pulls the server. Doing so will put you in control over the app and the server behind it, but you can still use CDN for what it was meant for – serving static content.

    Reply
  5. 5
    Debloper@email.null'

    Debloper

    Symlink your 404 page to the index page. That way, when a requested URL is not found on your web-content (about any link, as it appears in your case), the 404 page is served, which is in turn the index page itself.

    # ln -s index.html 404.html

    Reply
  6. 6
    spinus@email.null'

    spinus

    Nginx http server can do this like:

    location /{
        # serve a file
    }
    

    or you can customize your links like

    location /my_html{
         # serve html file
    }
    
    location /cdn/{
         # serve rest files
    }
    

    you can even check urls by regexps

    location ~ /cdn/.*.js${
        # serve cdn
    }
    
    Reply
  7. 7
    moodh@email.null'

    moodh

    We recently contacted edgecast.com (which is a cdn like cloudfront) and through their support they told me that this is indeed something that they can do, but not through their standard interface. I was told to simply contact them when we needed a wildcard route to a single file.

    As for your your question: yes, it’s possible. Just contact them through their live chat and they’ll help you out, good luck!

    Some more (negative) information:
    A catch-all-rule like this means the stupid favicon.ico-forced-request some browsers (read IE) do will be caught and the regular html-page will be downloaded again. In fact, all automatic requests (iframes also request a favicon, for example) against the root-domain will be caught and the regular html-file will be downloaded. This may or may not be a problem for you but for me all these hidden requests is making me rethink the solution and using a webserver behind to do the actual catch-all. Shame really.

    Reply
  8. 8
    BenSwayne@email.null'

    BenSwayne

    CDNs are intended to deliver static content by serving the static resource from the closest geographical point possible to the client. CDN technology is not intended to do a redirect or server side processing of the request. You’ll need something else involved here to do that part. The question is just whether that is a server side technology or some sort of load balancer/firewall request re-writing (to avoid having a server side technology).

    I don’t think there is a truly platform agnostic way of doing this. You’ll always be tied to either a server side technology or a load balancer/firewall platform. But it also sounds like you may already have this constraint as you need somewhere to host your JSON API? Even if you haven’t decided on the platform, pretty much any platform should allow you to do some basic routing. If you can serve JSON Http requests, you should be able to do some page routing too.

    As a side note, I don’t believe you want to return your “index.html” from absolutely all possible URLs at your domain. You’ll want some list of valid URLs and invalid URLs. In which case you’ll need to be pinging your back end anyway to validate the request URL. That further suggests to me that a server side technology will be better suited for this task then a blind “catch-all” redirect at a lower level.

    My personal preference would be to use your favorite MVC framework to serve indexable content with your desired URL structure (pretty much all page loads) and then use your JSON api to work with that content after page load (any dynamic stuff you want to be able to do). The whole thing, both page loads and API, being served from the same server platform/environment.

    Reply
  9. 9
    Ja͢ck@email.null'

    Ja͢ck

    Any CDN should have the capability of defining an origin server. This server gets contacted by the CDN to serve the file if the edge location doesn’t have it.

    The good news is that the origin server can be anything that serves web pages, such as Apache, Nginx, etc. This means that you can apply any kind of rewriting rules you wish.

    If you don’t wish to set up the origin server yourself, you could look at hosting your (static) site on S3. Recently they have introduced web redirects which may help you to to serve the same file under a different “alias”. Failing that, you could look at redefining the standard error document, but I’m not sure whether an error status code will still be sent.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Copyright © 2017 SolutionMmyself.com