My normal use case is I type in the local IP address and login to the PrusaLink service. I check Start print after transfer and then drag and drop a g-code file to start printing immediately after the upload is complete.
As expected PrusaLink starts, and finishes uploading the g-code file BUT when it completes it reports an error code 414 as shown below. The g-code file does not arrive to the USB stick on the MK4 due to this. I suspect this is due to the file name being too long, and if that is the case I would expect PrusaLink to report this error immediately before attempting to upload especially since large files may take a while to transmit.
Steps to reproduce:
Open PrusaLink website
Drag and drop the g-code I have attached above
Observe the error when the upload is "complete"
Expected behavior:
PrusaLink uploads the file to the MK4 USB stick without any issues.
Actual behavior:
PrusaLink attempts to upload the file and after it should complete it reports 414: URI Too Long. And the g-code was not actually uploaded the MK4 USB stick. I am not sure if the technical limitations here can be blamed on PrusaLink or the MK4 firmware. But this error reporting feels like it should happen immediately before starting the upload process.
Ideas for improvements:
Report 414: URI Too Long before attempting to upload the G-code file.
Before raising 414 to the user, ask the user if the filename can be truncated.
Allow longer filenames.
Create a more detailed error message for 414 as the text URI Too Long or Action can not be performed doesn't tell me (the end user) much what went wrong. I'm just assuming its the filename is too long. It would be useful to see how long it can be in the message.
Various version info:
Attachments:
Description:
My normal use case is I type in the local IP address and login to the PrusaLink service. I check Start print after transfer and then drag and drop a g-code file to start printing immediately after the upload is complete.
As expected PrusaLink starts, and finishes uploading the g-code file BUT when it completes it reports an error code 414 as shown below. The g-code file does not arrive to the USB stick on the MK4 due to this. I suspect this is due to the file name being too long, and if that is the case I would expect PrusaLink to report this error immediately before attempting to upload especially since large files may take a while to transmit.
Steps to reproduce:
Expected behavior: PrusaLink uploads the file to the MK4 USB stick without any issues.
Actual behavior: PrusaLink attempts to upload the file and after it should complete it reports
414: URI Too Long. And the g-code was not actually uploaded the MK4 USB stick. I am not sure if the technical limitations here can be blamed on PrusaLink or the MK4 firmware. But this error reporting feels like it should happen immediately before starting the upload process.Ideas for improvements:
414: URI Too Longbefore attempting to upload the G-code file.URI Too LongorAction can not be performeddoesn't tell me (the end user) much what went wrong. I'm just assuming its the filename is too long. It would be useful to see how long it can be in the message.