[
https://issues.apache.org/jira/browse/SOLR-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966603#action_12966603
]
Fuad Efendi commented on SOLR-2262:
-----------------------------------
I tracked this problem down to
{code}
SolrDispatchFilter.doFilter...
...
String path = req.getServletPath();
if( req.getPathInfo() != null ) {
// this lets you handle /update/commit when /update is a servlet
path += req.getPathInfo();
}
{code}
My only guess is that _Tomcat 7 has a bug_ in
{code}
HttpServletRequest.getPathInfo()
{code}
According to Java 6 EE API,
{code}
getPathInfo() ... Returns any extra path information associated with the URL
the client sent when it made this request. The extra path information follows
the servlet path but precedes the query string and will start with a "/"
character.
{code}
> 404 on
> -------
>
> Key: SOLR-2262
> URL: https://issues.apache.org/jira/browse/SOLR-2262
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4.1
> Environment: Tomcat/7.0.4
> Reporter: Sean Timm
> Priority: Trivial
>
> Config and schema links from the admin page do not work with Tomcat 7.
> Apparently Tomcat 7 doesn't like the extra slash in the URL: file/? and
> returns a 404. Removing the extra / resolves the problem.
> Does not work:
> http://localhost:8080/solr/admin/file/?file=schema.xml
> Works:
> http://localhost:8080/solr/admin/file?file=schema.xml
> I stumbled across a blog post that provides a bit more detail.
> http://androidyou.blogspot.com/2010/09/tomcat-7-with-solr-14-http-status-404.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
