Closed itsacorn closed 6 years ago
This module no longer has a split in it. Perhaps it is fixed by now? Are you using the latest version of Express?
I updated everything, however i still get this error. It does not pop up each time, but only if i refresh the site rapidly.
Weird. As noted, there isn't even a split method call in this module to fix, so I don't know what to do. Any suggestions? Maybe you can help me reproduce the issue or something?
My setup is a NGINX proxy server, and a normal Express app with any route. Refresh the site rapidly and it should pop up.
I tried that and no error. I'm not sure if I have the same setup as you, becaude i am using the current versions of evrrything, and there is no split method in the code any more to even change. Can you hook a debugger to your server and track down the issue? Otherwise probably need mkre specific information to reproduce.
For now I'm going to close this, because our source code (https://github.com/jshttp/fresh/blob/master/index.js) doesn't contain noneMatch.split
, so there isn't even anything we could change directly with that stack trace. If you can either (a) provide complete, detailed reproduction steps or (b) a stack trace with the current version of this module, I can re-open. Any patch that is released would require you to upgrade to get it; upgrading to the actual current version would be a first step. If you can provide (a) I can always test if the current version of this module has the same issue.
Hello everyone, i have encountered an issue when using fresh in my web server based on express. I suspect that express automatically installed fresh. Here is the error:
Does anyone know why this happens? I am behind an NGINX proxy, if that is important.