https://issues.apache.org/bugzilla/show_bug.cgi?id=51799
--- Comment #3 from Remy Maucherat <r...@apache.org> 2011-09-21 14:21:13 UTC --- The behavior has never changed, has always been consistent, and nowhere in the specification does it say the path needs to exist. Unlike for getResource, where the behavior for a non existent resource is clearly defined as being different. So why is there any doubt about this ? If you didn't realize this could be used to create a file in the filesystem, then it would still be nice to not assume by default that the specification must be stupid because a user says so. And that, even if there wasn't any good reason at all, the change would *again* break plenty of existing applications. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- 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
