DO NOT REPLY [Bug 35853] - Make JkMount compatible with servlet-mapping/url-pattern in web.xml

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35853] - Make JkMount compatible with servlet-mapping/url-pattern in web.xml

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35853] New: - Make JkMount compatible with servlet-mapping/url-pattern in web.xml

gzilla/show_bug.cgi?id=35853 Summary: Make JkMount compatible with servlet-mapping/url-pattern in web.xml Product: Tomcat 4 Version: Unknown Platform: All OS/Version: other Status: NEW Severity:

DO NOT REPLY [Bug 34637] - Servlet Mapping validation doesn't comply to Servlet 2.4 spec

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34637] New: - Servlet Mapping validation doesn't comply to Servlet 2.4 spec

gzilla/show_bug.cgi?id=34637 Summary: Servlet Mapping validation doesn't comply to Servlet 2.4 spec Product: Tomcat 5 Version: 5.5.9 Platform: All OS/Version: All Status: NEW Severity: normal P

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 25338] - URI Rewrite does not function according to Servlet2.3 specifications (jsession= , servlet-mapping & filter-mapping)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 30535] - Servlet mapping fails when url includes semicolon

gzilla/show_bug.cgi?id=30535 Servlet mapping fails when url includes semicolon [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 30535] - Servlet mapping fails when url includes semicolon

gzilla/show_bug.cgi?id=30535 Servlet mapping fails when url includes semicolon --- Additional Comments From [EMAIL PROTECTED] 2004-08-12 08:23 --- Here the semicolon is used in the path part of the URL in it escaped form (%3B). As this is a valid url I think the match to "*.txt"

DO NOT REPLY [Bug 30535] - Servlet mapping fails when url includes semicolon

gzilla/show_bug.cgi?id=30535 Servlet mapping fails when url includes semicolon --- Additional Comments From [EMAIL PROTECTED] 2004-08-11 16:36 --- I think the Servlet Specification v2.4 doesn't mandate us to map URLs with colons, as that's a URL terminator. Can yo

DO NOT REPLY [Bug 30535] New: - Servlet mapping fails when url includes semicolon

gzilla/show_bug.cgi?id=30535 Servlet mapping fails when url includes semicolon Summary: Servlet mapping fails when url includes semicolon Product: Tomcat 5 Version: 5.0.19 Platform: PC OS/Version: Other Status: NEW Severity:

DO NOT REPLY [Bug 5759] - CGI servlet mapping by extension *.cgi does not work

gzilla/show_bug.cgi?id=5759 CGI servlet mapping by extension *.cgi does not work [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RE

DO NOT REPLY [Bug 25338] New: - URI Rewrite does not function according to Servlet2.3 specifications (jsession= , servlet-mapping & filter-mapping)

gzilla/show_bug.cgi?id=25338 URI Rewrite does not function according to Servlet2.3 specifications (jsession= , servlet-mapping & filter-mapping) Summary: URI Rewrite does not function according to Servlet2.3 specifications (jsession= , servlet-mappin

DO NOT REPLY [Bug 23428] - servlet-mapping invoker

gzilla/show_bug.cgi?id=23428 servlet-mapping invoker [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 23428] New: - servlet-mapping invoker

gzilla/show_bug.cgi?id=23428 servlet-mapping invoker Summary: servlet-mapping invoker Product: Tomcat 5 Version: 5.0.12 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Com

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2003-09-13 14:13 --- Also in relation to TOMCAT-4.0.6 on OS/390 USS, the combination of TOMCAT-4.0.6 and JBOSS-2.4.10 has been tested on OS/390 USS (only preliminary

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2003-09-13 13:48 --- Created an attachment (id=8197) attachment file #3 for binary fix of bug 13014 on tomcat

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2003-09-13 13:16 --- There is another patch that fixes some bugs observed in Tomcat-4.0.6 operating on OS/390 USS (like working with manager , basic authentication ,etc) t

DO NOT REPLY [Bug 22108] - WebDAV not working with "default" servlet mapping

gzilla/show_bug.cgi?id=22108 WebDAV not working with "default" servlet mapping [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 22108] New: - WebDAV not working with "default" servlet mapping

gzilla/show_bug.cgi?id=22108 WebDAV not working with "default" servlet mapping Summary: WebDAV not working with "default" servlet mapping Product: Tomcat 5 Version: 5.0.6 Platform: PC OS/Version: Windows NT/2K Stat

Re: [PROPOSAL] Expose pre-compiled JSPs without servlet mapping

Petr Jiricka wrote: Remy Maucherat wrote: Jan Luehe wrote: Currently, if webapp developers do not want to expose the source of their JSP files, they have to precompile them and add a servlet mapping for each JSP to their web.xml (e.g., with the help of jspc). If the webapp contains a large

Re: [PROPOSAL] Expose pre-compiled JSPs without servlet mapping

Remy Maucherat wrote: Jan Luehe wrote: Currently, if webapp developers do not want to expose the source of their JSP files, they have to precompile them and add a servlet mapping for each JSP to their web.xml (e.g., with the help of jspc). If the webapp contains a large number of JSPs, the

Re: [PROPOSAL] Expose pre-compiled JSPs without servlet mapping

Jan Luehe wrote: Tim Funk wrote: How will phantom pages be addressed? Pages where the jsp once existed but then was deleted, but the corresponding class was not deleted? That's why I suggested an option for JspServlet that would disable this "optimization" and require a serv

Re: [PROPOSAL] Expose pre-compiled JSPs without servlet mapping

Tim Funk wrote: How will phantom pages be addressed? Pages where the jsp once existed but then was deleted, but the corresponding class was not deleted? That's why I suggested an option for JspServlet that would disable this "optimization" and require a servlet mapping for each

Re: [PROPOSAL] Expose pre-compiled JSPs without servlet mapping

Jan Luehe wrote: Currently, if webapp developers do not want to expose the source of their JSP files, they have to precompile them and add a servlet mapping for each JSP to their web.xml (e.g., with the help of jspc). If the webapp contains a large number of JSPs, the web.xml is going to grow

Re: [PROPOSAL] Expose pre-compiled JSPs without servlet mapping

How will phantom pages be addressed? Pages where the jsp once existed but then was deleted, but the corresponding class was not deleted? -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL

[PROPOSAL] Expose pre-compiled JSPs without servlet mapping

Currently, if webapp developers do not want to expose the source of their JSP files, they have to precompile them and add a servlet mapping for each JSP to their web.xml (e.g., with the help of jspc). If the webapp contains a large number of JSPs, the web.xml is going to grow pretty big. Would it

DO NOT REPLY [Bug 18658] - HTTP 404 when welcome-file doesn't exist but servlet-mapping exists

gzilla/show_bug.cgi?id=18658 HTTP 404 when welcome-file doesn't exist but servlet-mapping exists [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 18658] New: - HTTP 404 when welcome-file doesn't exist but servlet-mapping exists

gzilla/show_bug.cgi?id=18658 HTTP 404 when welcome-file doesn't exist but servlet-mapping exists Summary: HTTP 404 when welcome-file doesn't exist but servlet- mapping exists Product: Tomcat 4 Version: 4.1.18 Platform: PC O

DO NOT REPLY [Bug 16243] - deploy fails because web.xml in manager fails to specify /deploy as a servlet mapping

gzilla/show_bug.cgi?id=16243 deploy fails because web.xml in manager fails to specify /deploy as a servlet mapping [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 16243] - deploy fails because web.xml in manager fails to specify /deploy as a servlet mapping

gzilla/show_bug.cgi?id=16243 deploy fails because web.xml in manager fails to specify /deploy as a servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2003-01-19 18:44 --- Created an attachment (id=4491) manager web.xml which supports the "deploy" command -- To uns

DO NOT REPLY [Bug 16243] New: - deploy fails because web.xml in manager fails to specify /deploy as a servlet mapping

gzilla/show_bug.cgi?id=16243 deploy fails because web.xml in manager fails to specify /deploy as a servlet mapping Summary: deploy fails because web.xml in manager fails to specify /deploy as a servlet mapping Product: Tomcat 4 Version: U

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-12-03 19:36 --- Created an attachment (id=4028) Revisions to getReporter() so that encoding is observed -- To unsubscribe, e-mail: <mailto:[EMAIL PROTEC

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-12-03 19:33 --- After applying the changes described by Seyed Ali Madani, and rebuilding Tomcat, (and converting several script files, etc. to EBCDIC) I can confirm

Re: 4.0 and 4.1 servlet-mapping

Mladen Turk wrote: Hi, Probably shuld, but I hate to STWF ;). In 4.0 the /app/WEB-INF/classes/ were mapped to the /app/servlet/ In 4.1 I need explicitly to put the invoker /servlet/* So that can work. Is this correct behaviour for 4.1 or I'm I missing something? The inv

4.0 and 4.1 servlet-mapping

Hi, Probably shuld, but I hate to STWF ;). In 4.0 the /app/WEB-INF/classes/ were mapped to the /app/servlet/ In 4.1 I need explicitly to put the invoker /servlet/* So that can work. Is this correct behaviour for 4.1 or I'm I missing something? MT. -- To unsubsc

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-24 10:35 --- There are obvious benefits to using the platform encoding to read the config files, so we'll have to consider if that kind of patch will be mer

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-24 10:15 --- Remy Maucherat, what next ? How does it work ? Someone would pick up from Ali's suggested fix and incorporate into the next distribution ? W

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-24 10:02 --- Hi all I wrote the detailed instructions for using binary fixes for tomact 4.0.6 in response to someone ask me in OE mailing list which appended below,a

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-24 09:51 --- Created an attachment (id=3597) attachment file #2 for binary fix of bug 13014 on tomcat 4.0.6 -- To unsubscribe, e-mail: <mailto:tomcat-dev-un

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-24 09:48 --- Created an attachment (id=3596) attachment file #1 for binary fix of bug 13014 on tomcat 4.0.6 -- To unsubscribe, e-mail: <mailto:tomcat-dev-un

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-24 07:10 --- Usually, what happens is that someone contributes a patch. -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> Fo

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-24 06:50 --- What is the procedure for distributing a fix as described by Seyed Ali Madani ? The fix is for v4.0.6 but the problem is reported under v4.1.10

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-23 17:57 --- Ali, What a great news ! Is it possible to ftp the binary directly from your web site ? Joseph Tan -- To unsubscribe, e-mail: <mailto:t

Servlet Mapping xss Bug

Hi, I'm not sure if this is the correct list to post to so.. apologies ahead of time. When testing for this vulnerability Bugtraq id 5193, via a request such as http://target/servlet/org.apache.catalina.ContainerServlet/alert("css-test") A " javax.servlet.ServletException: ..." is generated; is

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-23 16:19 --- Hi everybody The same problem you described exists on 4.0.6 ,so I fixed the bugs and now I have the TOMCAT 4.0.6 operating perfectly on OS/390 2.10 .

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-09 15:11 --- The USS environment is somewhat unusual...perhaps no one at apache.org has ready access to such a system for testing and debugging this issue. Atta

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-09 07:13 --- I posted the apparently offending code to see if anyone would have an idea (I don't). It would look like the test .startsWith("/"

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-09 06:52 --- Remy, How can I help in correcting this bug ? I am no Java programmer. It is clumsy but can you give me instructions that I can carry out at my

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-09 06:27 --- The idea is that maybe no member of the dev team has access to the appropriate machine and can reproduce this. The offending code looks li

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-10-09 03:11 --- Ned, We can live with version 331 for the time being until it is fixed. Have you found the source of this bug ? If so, is there any work around ? The

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PRO

DO NOT REPLY [Bug 13014] - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping --- Additional Comments From [EMAIL PROTECTED] 2002-09-27 19:25 --- I replaced the XML parser with xercesImpl.jar from Xerces-Java 2.1.0. The problem remains. I installed v331 of tomcat today and it works after wi

DO NOT REPLY [Bug 13024] - Servlet Mapping error ?

gzilla/show_bug.cgi?id=13024 Servlet Mapping error ? [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Reso

DO NOT REPLY [Bug 13024] - Servlet Mapping error ?

gzilla/show_bug.cgi?id=13024 Servlet Mapping error ? [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORK

DO NOT REPLY [Bug 13024] - Servlet Mapping error ?

gzilla/show_bug.cgi?id=13024 Servlet Mapping error ? [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 13024] New: - Servlet Mapping error ?

gzilla/show_bug.cgi?id=13024 Servlet Mapping error ? Summary: Servlet Mapping error ? Product: Tomcat 4 Version: 4.1.12 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Com

DO NOT REPLY [Bug 13014] New: - OS/390/USS - Invalid  in servlet mapping

gzilla/show_bug.cgi?id=13014 OS/390/USS - Invalid  in servlet mapping Summary: OS/390/USS - Invalid in servlet mapping Product: Tomcat 4 Version: 4.1.10 Platform: Other OS/Version: Other Status: UNCONFIRMED Severity: B

DO NOT REPLY [Bug 11919] - Can't create servlet-mapping of "/" (not "/*")

gzilla/show_bug.cgi?id=11919 Can't create servlet-mapping of "/" (not "/*") --- Additional Comments From [EMAIL PROTECTED] 2002-08-27 03:53 --- Then, how can I map / only (not /*) to a particular Servlet? By use filter? Thanks. -- To unsubscribe, e-mail:

DO NOT REPLY [Bug 11919] New: - Can't create servlet-mapping of "/" (not "/*")

gzilla/show_bug.cgi?id=11919 Can't create servlet-mapping of "/" (not "/*") Summary: Can't create servlet-mapping of "/" (not "/*") Product: Tomcat 4 Version: 4.0.4 Final Platform: PC OS/Version:

DO NOT REPLY [Bug 5759] - CGI servlet mapping by extension *.cgi does not work

gzilla/show_bug.cgi?id=5759 CGI servlet mapping by extension *.cgi does not work [EMAIL PROTECTED] changed: What|Removed |Added Component|Catalina|Servlets:CGI

DO NOT REPLY [Bug 6846] - dispatcher.forward() is confused when using special servlet mapping URLs

gzilla/show_bug.cgi?id=6846 dispatcher.forward() is confused when using special servlet mapping URLs [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 6846] - dispatcher.forward() is confused when using special servlet mapping URLs

gzilla/show_bug.cgi?id=6846 dispatcher.forward() is confused when using special servlet mapping URLs --- Additional Comments From [EMAIL PROTECTED] 2002-03-04 14:03 --- Created an attachment (id=1273) web application that demonstrates the bug. just should be able to put this in the w

DO NOT REPLY [Bug 6846] New: - dispatcher.forward() is confused when using special servlet mapping URLs

gzilla/show_bug.cgi?id=6846 dispatcher.forward() is confused when using special servlet mapping URLs Summary: dispatcher.forward() is confused when using special servlet mapping URLs Product: Tomcat 4 Version: 4.0.3 Final Platform: PC

DO NOT REPLY [Bug 6032] - Accessing a jsp directly behaves differently than accessing through a servlet-mapping.

gzilla/show_bug.cgi?id=6032 Accessing a jsp directly behaves differently than accessing through a servlet-mapping. [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 6032] New: - Accessing a jsp directly behaves differently than accessing through a servlet-mapping.

gzilla/show_bug.cgi?id=6032 Accessing a jsp directly behaves differently than accessing through a servlet-mapping. Summary: Accessing a jsp directly behaves differently than accessing through a servlet-mapping. Product: Tomcat 4 Version: 4.0.1

DO NOT REPLY [Bug 5759] - CGI servlet mapping by extension *.cgi does not work

gzilla/show_bug.cgi?id=5759 CGI servlet mapping by extension *.cgi does not work [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|RE

DO NOT REPLY [Bug 5759] - CGI servlet mapping by extension *.cgi does not work

gzilla/show_bug.cgi?id=5759 CGI servlet mapping by extension *.cgi does not work [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 5759] New: - CGI servlet mapping by extension *.cgi does not work

gzilla/show_bug.cgi?id=5759 CGI servlet mapping by extension *.cgi does not work Summary: CGI servlet mapping by extension *.cgi does not work Product: Tomcat 4 Version: 4.0.1 Final Platform: PC OS/Version: FreeBSD Status: NEW Se

DO NOT REPLY [Bug 4857] - web.xml file parse error if servlet-mapping comes before servlet

gzilla/show_bug.cgi?id=4857 web.xml file parse error if servlet-mapping comes before servlet [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 4857] New: - web.xml file parse error if servlet-mapping comes before servlet

gzilla/show_bug.cgi?id=4857 web.xml file parse error if servlet-mapping comes before servlet Summary: web.xml file parse error if servlet-mapping comes before servlet Product: Tomcat 4 Version: 4.0.1 Final Platform: PC OS/Version:

DO NOT REPLY [Bug 4362] - Reading init-params from a JSP should not need a servlet-mapping

gzilla/show_bug.cgi?id=4362 Reading init-params from a JSP should not need a servlet-mapping [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|

DO NOT REPLY [Bug 4362] - Reading init-params from a JSP should not need a servlet-mapping

gzilla/show_bug.cgi?id=4362 Reading init-params from a JSP should not need a servlet-mapping --- Additional Comments From [EMAIL PROTECTED] 2001-10-31 09:14 --- Remy's analysis of how init parameters work is correct. To put it in more general terms: * is a sub-element of .

DO NOT REPLY [Bug 4362] - Reading init-params from a JSP should not need a servlet-mapping

gzilla/show_bug.cgi?id=4362 Reading init-params from a JSP should not need a servlet-mapping [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RE

DO NOT REPLY [Bug 4362] - Reading init-params from a JSP should not need a servlet-mapping

gzilla/show_bug.cgi?id=4362 Reading init-params from a JSP should not need a servlet-mapping [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|RE

[PATCH] TC3.3b2 - Invalid servlet-mapping in web.xml file generated by JspC

JspC bugs recently fixed in Tomcat 4.0 also exist in 3.2 cvs diff -u JspC.java (in directory D:\jakarta-tomcat\jakarta-tomcat\src\share\org\apache\jasper) Index: JspC.java === RCS file: /home/cvspublic/jakarta-tomcat/src/share/org/a

RE: [PATCH] Fixes servlet-mapping in web.xml file generated by JspC u sing the -webxml and -webinc options

27;)); mappingout.write("\n\t\n"); } *CVS exited normally with code 1* -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Friday, September 07, 2001 2:04 PM To: '[EMAIL PROTECTED]' Subject: Re: [PATCH] Fix

Re: [PATCH] Fixes servlet-mapping in web.xml file generated by JspCu sing the -webxml and -webinc options

o: [EMAIL PROTECTED] > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > Subject: [PATCH] Fixes servlet-mapping in web.xml file generated by JspC > u sing the -webxml and -webinc options > > This patch fixes the following bug reports. Testing on Windows 2000

[PATCH] Fixes servlet-mapping in web.xml file generated by JspC using the -webxml and -webinc options

This patch fixes the following bug reports. Testing on Windows 2000 w/ SP2, JDK 1.3.1, and jakarta-tomcat-4.0-20010906. web.xml file generated by JspC is not valid as defined by DTD. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3474 Invalid url-pattern for servlet-mapping in web.xml file

servlet mapping to root of the site and different web-app contexts

et to the root of that context (that was pretty straightforward). For the images, I have defined another web-app context. However, when loading up page, none of the images show up... So, most probably, Tomcat is not overriding the servlet mapping with the context mappings... Is it my stupidity or

Servlet Mapping problem

Greetings I apologize if this question has been answered properly in other place but i'm unable to fix this problem :( I'm trying to mapp a Servlet to the following url: http://localhost/HolaMundo And i added the following to the WEB_INF/web.xml file: Hola Mundo 30 HolaMundo

Servlet Mapping

Hi I have several servlets which have been developed using a Apache JServe setup. I'm moving over to Tomcat with Apache and which to use the packaged servets that I already have. My problem is as follows: The servlet: /usr/local/tomcat/webapps/ROOT/WEB-INF/classes/IsItWorkingServlet works fine

Re: [BUG] servlet-mapping breaks after misrequest

On Sat, 11 Nov 2000, Craig R. McClanahan wrote: > Hi Jeff, > > Well, your reported behavior is definitely repeatable. But, after analyzing > it, my conclusion is "user error ... don't do that". > [snip "bug" report] > > What do you think? Fine :) I think it might be worth a FAQ entry though

Re: [BUG] servlet-mapping breaks after misrequest

for /tomcatbug/test.xyz, by the way. This was a separate issue. > > 8) Move ~/tomcatbug~ to ~/tomcatbug Note that Tomcat is *not* restarted at this point. If it was, you would not see the behavior discussed -- it would be just like step (4) above. > > 9) Request date.xyz. You'll

[BUG] servlet-mapping breaks after misrequest

Hi, Sorry if someone's reported this before, I just found a bug that affects (at least) Tomcat 3.2b3 up to 3.3dev from CVS. The bug lets the user see the source for files mapped to servlets via the tag in web.xml. The bug usually occurs during development, so it shouldn't be an issue with stabl