3 ms·
If i'm not wrong, cloudfront actually follows 302 redirects internally instead of passing the redirect on to the client. but since ?_escaped_fragment_= is a su
by ponyfleisch 10y ago
If i'm not wrong, cloudfront actually follows 302 redirects internally instead of passing the redirect on to the client.
but since ?_escaped_fragment_= is a suffix, not a prefix, i don't think redirection rules help.
- Alex3917 10y agoConfusingly, _escaped_fragment_= is always a prefix if you have a #! in your url, otherwise I think it can come anywhere in the URL params.[1] Here is the exact system of redirects we were using, along with an explanation of why it didn't work: https://www.fwdeveryone.com/t/mdDouBesQwCv0za_o7GjCA/serving-prerendered-s3-sites https://www.fwdeveryone.com/t/mdDouBesQwCv0za_o7GjCA/serving... [1] https://prerender.io/js-seo/angularjs-seo-get-your-site-indexed-and-to-the-top-of-the-search-results/ https://prerender.io/js-seo/angularjs-seo-get-your-site-inde...
- ponyfleisch 10y agoAh, yes, if you use #!. In that case, can't you do a cloudfront custom behaviour on /?_escaped_fragment_=*? I havent't tried this.