I guess that is because of the new TUS protocol use in the Uppy plugin we use for file upload.
The thing is it seems to work in NG2 but not in NG1 so i think we mis some setting/configuration in the ng1 multi file upload component
2022-01-06 11:54 http-nio-8080-exec-861 WARN me.desair.tus.server.TusFileUploadService Unable to process request POST http://xxxxx.yyyyy.com/TSP/tus/upload/2/tspDocumentUpload__A0CCE91E_38C5_47D7_81F8_A0248E6D9BE2/mfUpload/onFileUploaded/. Sent response status 405 with message "POST requests have to be sent to '/tus/upload/[0-9]+/.+/.+/.+/'. "
steve1376656734 wrote:We have another major issue with the MultiFileUpload component. If you deploy to a server context other than ROOT you cannot upload any files and you get the following error in the logs:
- Code: Select all
2022-01-06 11:54 http-nio-8080-exec-861 WARN me.desair.tus.server.TusFileUploadService Unable to process request POST http://xxxxx.yyyyy.com/TSP/tus/upload/2/tspDocumentUpload__A0CCE91E_38C5_47D7_81F8_A0248E6D9BE2/mfUpload/onFileUploaded/. Sent response status 405 with message "POST requests have to be sent to '/tus/upload/[0-9]+/.+/.+/.+/'. "
It seems that the context element of the URL is messing up the check that the server is doing on the POST request.
If you deploy the same WAR file to a ROOT context then it works fine.
Users browsing this forum: No registered users and 0 guests