https://bz.apache.org/bugzilla/show_bug.cgi?id=60802
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |WONTFIX
--- Comment #4 from Mark Thomas <ma...@apache.org> ---
I thought this had been discussed a little before
https://bz.apache.org/bugzilla/show_bug.cgi?id=54971#c3
>From (rather hazy) memory, the reason for that was that Commons File Upload
allowed absolute paths and Tomcat allowing it here eased the migration path.
I'll add that the spec doesn't say how to handle the application passing an
absolute path. You could make the case that the behaviour is undefined and in
that case and the container is free to do as it chooses. Equally, you could
argue anything that isn't a relative file name is an error that should trigger
an IOException. At the extreme, you could argue anything that isn't a pure
filename with no path is an error.
I don't see any discussion around this particular point in the Servlet EG. Now
is certainly the time to open an issue if you'd like clarification since the EG
is fairly active at the moment.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
