You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for creating this. I love this approach to v2 routing. I converted my application over to embrace it and unfortunately when I deployed on S3 my route files were 404/AccessDenied. I delved into this further and even though I can create a path in the bucket with the +, S3 requires those assets to be requested with the + URL encoded to %3D. I asked in Remix Discord if there was a way to rewrite asset imports but there isn't. I had to resolve my problem using a terminal - convention instead of the terminal + and hard-coded - into my clone of the repo. If this issue is of wider appeal and I'm not missing anything obvious, I can work a proper PR for configurability of this.
The text was updated successfully, but these errors were encountered:
Thanks for creating this. I love this approach to v2 routing. I converted my application over to embrace it and unfortunately when I deployed on S3 my route files were 404/AccessDenied. I delved into this further and even though I can create a path in the bucket with the
+
, S3 requires those assets to be requested with the+
URL encoded to%3D
. I asked in Remix Discord if there was a way to rewrite asset imports but there isn't. I had to resolve my problem using a terminal-
convention instead of the terminal+
and hard-coded-
into my clone of the repo. If this issue is of wider appeal and I'm not missing anything obvious, I can work a proper PR for configurability of this.The text was updated successfully, but these errors were encountered: