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
Describe the bug
I created a function as explained in https://github.com/butlerx/wetty/blob/main/docs/downloading-files.md (by the way, I am not sure why it is being overly complex - at least in my attempt, I managed to convert the function so I can just call 'dl ' and reach the same (non working :)) result which I get if I follow the instructions above... (basically replacing /dev/stdin with "$1")
Anyway...
I get a popup indeed, if you can call it that way, it's more of a 'div' in the right-bottom corner of that screen. That div shows HTML text that, if acted upon as actual HTML, would have probably worked (selecting the blob: and right clicking it and then choosing "Go to URL" does show the full file on the screen), but probably (?) somehow this HTML is escaped so code is shown instead of actual link.
Example of text I see: Download ready: <a href="blob:https://192.168.92.151/191268c5-5312-4e5c-ad07-7d10eba1456c" target="_blank" download="file-20220407181636.txt">file-20220407181636.txt</a>
Screenshots
Desktop (please complete the following information):
OS: Arch Linux
Browser: Chromium 100.0.4896.75, Firefox 99.0 (exactly the same behavior)
Additional context
WeTTY runs under Nginx reverse proxy, if it matters. I have a sense that once websocket kicked in, this shouldn't/can't influence anything, but I'm mentioning it anyway :)
WeTTY itself runs on NodeJS v16.14.2
The text was updated successfully, but these errors were encountered:
Describe the bug
I created a function as explained in https://github.com/butlerx/wetty/blob/main/docs/downloading-files.md (by the way, I am not sure why it is being overly complex - at least in my attempt, I managed to convert the function so I can just call 'dl ' and reach the same (non working :)) result which I get if I follow the instructions above... (basically replacing /dev/stdin with "$1")
Anyway...
I get a popup indeed, if you can call it that way, it's more of a 'div' in the right-bottom corner of that screen. That div shows HTML text that, if acted upon as actual HTML, would have probably worked (selecting the blob: and right clicking it and then choosing "Go to URL" does show the full file on the screen), but probably (?) somehow this HTML is escaped so code is shown instead of actual link.
Example of text I see:
Download ready: <a href="blob:https://192.168.92.151/191268c5-5312-4e5c-ad07-7d10eba1456c" target="_blank" download="file-20220407181636.txt">file-20220407181636.txt</a>
Screenshots
Desktop (please complete the following information):
Additional context
WeTTY runs under Nginx reverse proxy, if it matters. I have a sense that once websocket kicked in, this shouldn't/can't influence anything, but I'm mentioning it anyway :)
WeTTY itself runs on NodeJS v16.14.2
The text was updated successfully, but these errors were encountered: