Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Why...........? Commented Feb 19, 2020 at 15:46
  • @user253751 using an arbitrary string to detect when an URI is looking for assets could be easier and more reliable than filtering by file extension. Commented Feb 20, 2020 at 10:33
  • But why not just use the actual path? Instead of telling the browser to fetch /a/b/c/foo.css and then rewriting it to /public/foo.css why not tell the browser to fetch /public/foo.css? Commented Feb 20, 2020 at 10:37
  • @user253751 The idea was to link assets with /_front/foo.css which would rewrite to /public/foo.css to avoid rewriting to the Front Controller like /public/index.php?_url=/public/foo.css. But I think I was wrong about my .htaccess configuration at the time I wrote that, this can be served directly, only the application should write the correct path to the assets. Commented Feb 20, 2020 at 10:44