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
Since we are trying to move from .htaccess to php routing, it would be very convenient if this extension was also usable for routes to static assets like JS and CSS files.
For instance, it is bad practice to request your styles with a querystring: style.css?v=204, incorporating it into the name is better: style-204.css. This is because some caching proxies will not cache the file when there is a query parameter present.
However, to do so a route is needed (a redirect will not work, as then the destination will still be cached), but at this moment routes only work for Symphony pages - not for files in the filesystem. Leaving me with no other option than to add the route to the server config - which is something I really, really want to stop doing.
The text was updated successfully, but these errors were encountered:
For instance, it is bad practice to request your styles with a querystring: style.css?v=204, incorporating it into the name is better: style-204.css. This is because some caching proxies will not cache the file when there is a query parameter present.
Now that is interesting. Thanks or pointing this out.
Since we are trying to move from
.htaccess
tophp
routing, it would be very convenient if this extension was also usable for routes to static assets like JS and CSS files.For instance, it is bad practice to request your styles with a querystring:
style.css?v=204
, incorporating it into the name is better:style-204.css
. This is because some caching proxies will not cache the file when there is a query parameter present.However, to do so a route is needed (a redirect will not work, as then the destination will still be cached), but at this moment routes only work for Symphony pages - not for files in the filesystem. Leaving me with no other option than to add the route to the server config - which is something I really, really want to stop doing.
The text was updated successfully, but these errors were encountered: