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
Is your feature request related to a problem? Please describe.
My AMD module loader automatically adds a ?t=<timestamp> query string to loaded modules as a cache buster. This query string causes the client serving to fail, returning a JSON with message: transport unknown.
Describe the solution you'd like
I'd like that the detection of requests for the client JS ignores the query string.
Describe alternatives you've considered
I could serve the client manually, but this might cause the versions of the server and client to diverge. I could also strip the query string using a reverse proxy, but this creates additional moving parts where none should be.
Additional context
n/a
The text was updated successfully, but these errors were encountered:
TimWolla
changed the title
Support an arbitrary query string when serving the client JavaScript
Support an arbitrary query string (cache buster) when serving the client JavaScript
Jul 17, 2021
Is your feature request related to a problem? Please describe.
My AMD module loader automatically adds a
?t=<timestamp>
query string to loaded modules as a cache buster. This query string causes the client serving to fail, returning a JSON withmessage: transport unknown
.Describe the solution you'd like
I'd like that the detection of requests for the client JS ignores the query string.
Describe alternatives you've considered
I could serve the client manually, but this might cause the versions of the server and client to diverge. I could also strip the query string using a reverse proxy, but this creates additional moving parts where none should be.
Additional context
n/a
The text was updated successfully, but these errors were encountered: