Also, I am finding quite a few of these "generic" errors in my logs
(Error uploading: {0}!), and I believe it's happening when the upload
fails either through a broken pipe/connection or client abort. I
haven't had the time to test it though to be sure why these are being
generated in my error logs.
------ Original Message ------
From "Burton Rhodes" <burtonrho...@gmail.com>
To "Struts Developers List" <dev@struts.apache.org>
Date 2/9/2024 9:38:12 AM
Subject Re: [7.0.0-M3] Error message
The easiest example is when a custom "saveDir" is not accessible. (e.g. no
security access). This will throw a generic FileUploadException with no identifiable
file.
------ Original Message ------
From "Lukasz Lenart" <lukaszlen...@apache.org>
To "Struts Developers List" <dev@struts.apache.org>
Date 2/9/2024 9:34:36 AM
Subject Re: [7.0.0-M3] Error message
pt., 9 lut 2024 o 16:21 Burton Rhodes <burtonrho...@gmail.com> napisał(a):
I haven't had time yet, but I will try this weekend.
Could you share a use case when it can happen?
Cheers
Lukasz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
