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
Hey! I think I have found an issue with Remix but I'm not exactly sure. I think it affects most of Remix based apps.
Basically what's happening is that when I visit a remix based app (for example mine or Daffy.com (@sergiodxa )), the developer tools start fetching source maps. Even if they don't exist (404), the response is delayed significantly (daffy.com from 300ms to over 4.5 seconds), mine from 200ms to 2s at minimum. I don't have any data to prove that this could be used for example for (D)DOS.
I have tried to use a simple middleware to filter any requests requesting *.js.map and it's solved.
I also have another issue and that's that sometimes for some people regardless of a route, the browser is spinning and doesn't receive a response from the server. So far it happened only on an initial request and not subsequent route navigation. Logs showing that the request completed but that's all. I'm not sure if these are related but this is my observation. We currently have 1200 registered users so misconfigured server is probably not an option.
Regarding the source maps, is it something that remix team can fix?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey! I think I have found an issue with Remix but I'm not exactly sure. I think it affects most of Remix based apps.
Basically what's happening is that when I visit a remix based app (for example mine or Daffy.com (@sergiodxa )), the developer tools start fetching source maps. Even if they don't exist (404), the response is delayed significantly (daffy.com from 300ms to over 4.5 seconds), mine from 200ms to 2s at minimum. I don't have any data to prove that this could be used for example for (D)DOS.
I have tried to use a simple middleware to filter any requests requesting *.js.map and it's solved.
I also have another issue and that's that sometimes for some people regardless of a route, the browser is spinning and doesn't receive a response from the server. So far it happened only on an initial request and not subsequent route navigation. Logs showing that the request completed but that's all. I'm not sure if these are related but this is my observation. We currently have 1200 registered users so misconfigured server is probably not an option.
Regarding the source maps, is it something that remix team can fix?
Beta Was this translation helpful? Give feedback.
All reactions