Marcus Ahlberg

Cool! I will investigate that. Another idea I came up with was that if we would upload the files in the following order: 1. js/json-files 2. html-files 3. Delete previous...

Hi @drestrepom , No, unfortunately, we haven't solved this yet. It's a bit complex as we need to reconfigure our bucket-origin in our CloudFront configuration (if we would publish new...

Hi, Yes, it normally works for other files (the error is thrown after some files have been uploaded).

Actually, now when I'm looking at it, we do not escape the characters in the `node.fields.slug`-field, so the value of that is actually: `'/argument-för-testning/p/123456/'`, which is the path that is...

Added encoding and it seems to work much better. However, that seems to me as an inconsistency compared to how gatsby's `createPage` works. Also, a better error message would be...

No, we are incrementally migrating our site to gatsby. So the bucket has the same structure as of being served from the root. So for example if someone requests `/our-gatsby-pages/*`...

Ah cool! Didn't know about `pathPrefix`, but that's right we are only using the `assetPrefix`. Thanks, that looks promising will test that out. I guess this kind of ends with...

Cool! Totally agree with you, haven't seen that the gatsby docs suggesting to use the `assetPrefix` for the same domain so maybe that's a hack by us, but it's working...

Have the same issue, can't find any issues in my onPostBuild :'(

I think I found the issue. I was creating ~20k redirects without having the flag `generateRedirectObjectsForPermanentRedirects` set to true, that fixed my issue