title: "Fetch as Google" doesn't load React routes on S3 with CloudFront
body: <p>I have a react-router site on Amazon S3, with 404 redirects set to hit index.html, where they find the code they need and the site does what it should.</p>
  
  <p>In Google Webmaster Tools, "Fetch as Google" for one of the routes gave error status: Not Found.</p>
  
  <p>I <a href="http://aserafin.pl/2016/03/23/react-router-on-amazon-s3/" rel="noreferrer">set up Cloudfront</a> for that origin with a Custom Error Response (404 to 200, with Response Page Path /index.html).</p>
  
  <p>But "Fetch as Google" for one of the routes still shows error status: Not Found.</p>
  
  <p>In Chrome or with curl, when I load <a href="http://[bucketname].s3-website-us-west-2.amazonaws.com/list/listname/username" rel="noreferrer">http://[bucketname].s3-website-us-west-2.amazonaws.com/list/listname/username</a> I see a 404 but the page then loads as expected.</p>
  
  <p>But when I load <a href="http://[randomchars].cloudfront.net/list/listname/username" rel="noreferrer">http://[randomchars].cloudfront.net/list/listname/username</a> I see a 200 with no re-direct and the page loads as expected.</p>
  
  <p>I've submitted a sitemap with the relevant URLs I'd like indexed and asked Google to crawl the site. It hasn't been crawled yet, but my best hope right now are a couple of suggestions I've seen that <a href="https://support.google.com/webmasters/answer/6066468?hl=en" rel="noreferrer">"Fetch as Google" won't follow redirects</a>, while Googlebot will when it actually crawls the site. I hope this is the case, but if I've missed any other obvious thing, I'd love to know. Thanks in advance!</p>