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
Hi, there is a bug when the zip url doesn't contain the file name / contains invalid characters. For example, our update server builds urls like htttp://example.com/build.php?id=545sdfsdff48sf1cv2, but the same error can be reproduced by just using a url like http://example.com/app.zip?lol.
The error is Error: ENOENT, open 'c:\TMPPATH\build.php?id=8965c9db76b64fb9421d153476b787b2' at Error (native). I guess it's because the computed filename isn't a valid file name.
Maybe a better approach would be to inspect the headers to find a Content-disposition? Althought right now the first response headers come in after the file name has been used to unlink & create the stream.
The text was updated successfully, but these errors were encountered:
Hi, there is a bug when the zip url doesn't contain the file name / contains invalid characters. For example, our update server builds urls like
htttp://example.com/build.php?id=545sdfsdff48sf1cv2
, but the same error can be reproduced by just using a url likehttp://example.com/app.zip?lol
.The error is
Error: ENOENT, open 'c:\TMPPATH\build.php?id=8965c9db76b64fb9421d153476b787b2' at Error (native)
. I guess it's because the computed filename isn't a valid file name.Maybe a better approach would be to inspect the headers to find a
Content-disposition
? Althought right now the first response headers come in after the file name has been used to unlink & create the stream.The text was updated successfully, but these errors were encountered: