This week's book giveaway is in the Design forum.
We're giving away four copies of Building Microservices and have Sam Newman on-line!
See this thread for details.
The moose likes Tomcat and the fly likes Extra Path Info weirdness Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Building Microservices this week in the Design forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Extra Path Info weirdness" Watch "Extra Path Info weirdness" New topic

Extra Path Info weirdness

Ulf Dittmer

Joined: Mar 22, 2005
Posts: 42958
I have a servlet XYZ that processes extra path info. But whenever extra path info is actually part of the URL, the servlet isn't called by Tomcat, and a 404 error message appears instead.



is routed to the servlet just fine, while


is incorrectly handled by Tomcat internally, no matter what the path info consists of.

Both requests show up in the access log just fine. The problem is not with extra path info in general, since the RequestInfoExample that ships with Tomcat works fine. Has anyone ever seen this?
Ben Souther

Joined: Dec 11, 2004
Posts: 13410

What are you using for a mapping?

Java API J2EE API Servlet Spec JSP Spec How to ask a question... Simple Servlet Examples jsonf
Ulf Dittmer

Joined: Mar 22, 2005
Posts: 42958
D'oh!. Thanks Ben, that was it. I had mapped to "/XYZ" instead of "/XYZ/*".
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: Extra Path Info weirdness
It's not a secret anymore!