Tomcat 5.0.25 does not honor error-page directive?
In a freshly unzipped jakarta-tomcat-5.0.25 installation I added error-page error-code404/error-code location/404.html/location /error-page (copied from servlet-2_4-fr-spec.pdf page 153) Just before the closing /web-app in webapps/ROOT/WEB-INF/web.xml I then copied a simple 404.html file to webapps/ROOT. However, when requesting some non existing page like http://127.0.0.1:8080/blub.jsp I get the standard browser 404 error page (in my case MSIE) not my 404.html. Is this a bug? Ciao - thanks - Det. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Tomcat 5.0.25 does not honor error-page directive?
I added the error-page tag to the end of the original webapps/ROOT/WEB-INF/web.xml (before /web-app). That even does match the order in the Deployment Descriptor Version 2.3. -Ursprüngliche Nachricht- Von: Rick Knowles [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 27. Mai 2004 13:20 An: Tomcat Developers List Betreff: Re: Tomcat 5.0.25 does not honor error-page directive? Sorry - just checked the file. There's only servlet and servlet-mapping elements. My bad Rick Knowles Detlef Pleiß wrote: In a freshly unzipped jakarta-tomcat-5.0.25 installation I added error-page error-code404/error-code location/404.html/location /error-page (copied from servlet-2_4-fr-spec.pdf page 153) Just before the closing /web-app in webapps/ROOT/WEB-INF/web.xml I then copied a simple 404.html file to webapps/ROOT. However, when requesting some non existing page like http://127.0.0.1:8080/blub.jsp I get the standard browser 404 error page (in my case MSIE) not my 404.html. Is this a bug? Ciao - thanks - Det. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WG: sorry, it's a browser problem - Tomcat 5.0.25 does not honor error-page directive?
-Ursprüngliche Nachricht- Von: Detlef Pleiß Gesendet: Donnerstag, 27. Mai 2004 15:18 An: '[EMAIL PROTECTED]' Betreff: AW: sorry, it's a browser problem - Tomcat 5.0.25 does not honor error-page directive? yes, thanks, it *is* a browser problem: It does work on Mac/Safari and it does work even in MSIE if I uncheck the friendly error messages. It just doesn't work with those friendly messages enabled in MSIE. Ciao - thanks - Det. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 27. Mai 2004 13:59 An: [iso-8859-1] Detlef Pleiß Betreff: Re: Tomcat 5.0.25 does not honor error-page directive? I then copied a simple 404.html file to webapps/ROOT. However, when requesting some non existing page like http://127.0.0.1:8080/blub.jsp I get the standard browser 404 error page (in my case MSIE) not my 404.html. Is this a bug? 1) (Trivial - sorry) have you the page 404.html with correct permissions? 2) Have you tried with other browsers? M$Exploder have bug (you may call it feature) so when your page is shorter than 512 bytes or so, it will display standard error page. You can also try check if you have display friendly error messages internet option disabled. best regards, Michal Kostrzewa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: sorry, it's a browser problem - Tomcat 5.0.25 does not ho nor error-page directive?
Confirmative, it does work, even in MSIE, with 1kb page. Thanks for your help and sorry for posting to the wrong list. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 27. Mai 2004 15:32 An: Detlef Pleiß Betreff: Re: AW: sorry, it's a browser problem - Tomcat 5.0.25 does not honor error-page directive? I'm glad I could help. Could you please post our conversation to the mailing list to mark this question answered? (I've sent this only to you, because my mail server is misconfigured and can't send emails to mailing lists) Also please note, if you make you error page longer (about 1 kilobyte will be enough) you will see this even with friendly messages enabled :) best regards, Michal Kostrzewa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5 - Proposal: move commons-fileupload-1.0.jar to common/li b
hello, Tomcat 5 comes with commons-fileupload-1.0.jar in server/lib. I believe it's in there as to make it available to the server/webapps admin and manager. Now I make use of commons fileupload in one of my normal webapps. But, as for the classloaders, that only works after moving commons-fileupload-1.0.jar from server/lib to common/lib. I don't use admin or manager, so I don't know, but believe, that moving fileupload to common should not break these. But, having fileupload in common would enable its immediate use for normal webapps. IMHO this could be documented in the RELEASE-NOTES just like how Xerces is available for web applications, that commons fileupload is available to web applications as well. BTW: the RELEASE-NOTES still speak of Xerces 2.6.0 is included where Xerces 2.6.2 is included with Tomcat 5.0.24. If I overlooked any good reason for not moving fileupload to common, I would be grateful to learn about it. ciao - thanks - Det. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Tomcat 5 - Proposal: move commons-fileupload-1.0.jar to commo n/lib
Hi Peter, used the shared/lib directory to add your web app shared jars to your catalina.base. My point is not about how to get it to work. My point is: if commons-fileupload-1.0.jar comes with the Tomcat installation anyway, why restrict its use by having it in the server directory. If it comes with the installation anyway, why not have it in a directory so normal web applications can use it right away without moving or copying anything around. ciao - Det. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Tomcat 5 - Proposal: move commons-fileupload-1.0.jar to commo n/lib
Because we strongly encourage webapps to be self-contained (all their dependencies in WEB-INF/lib). Things like the XML parser are the exception, not the rule. You don't need to move fileupload from server/lib to common/lib: you can leave it there for tomcat's internal use and put your own version in your webapp's WEB-INF/lib directory. ok, understood, thanks for your response! Your point about the Xerces version in the release note is good and will be addressed shortly. Thanks, Yoav Shapira Millennium Research Informatics -Original Message- From: Detlef Pleiß [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 4:58 AM To: 'Tomcat Developers List' Subject: AW: Tomcat 5 - Proposal: move commons-fileupload-1.0.jar to common/lib Hi Peter, used the shared/lib directory to add your web app shared jars to your catalina.base. My point is not about how to get it to work. My point is: if commons-fileupload-1.0.jar comes with the Tomcat installation anyway, why restrict its use by having it in the server directory. If it comes with the installation anyway, why not have it in a directory so normal web applications can use it right away without moving or copying anything around. ciao - Det. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
