lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-2022) request handler paths ending in "/" don't work with Tomcat 7
Date Wed, 27 Oct 2010 19:17:19 GMT

     [ https://issues.apache.org/jira/browse/SOLR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hoss Man updated SOLR-2022:
---------------------------

    Description: 
As originally reported in this thread...

http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat

Tomcat 7 has made changes in how URLs are resolved that result in the requests with paths
that end in a "/" character being given to the SolrDispatchFilter  with "index.jsp" appended
to them.  This results in SolrDispatchFilter being unable to correctly identify some situations
when a request should be processed by a request handler based on the name registered (ie:
"/update/csv/" is seen as "update/csv/index.jsp" so as a result the handler registered to
"/update/csv/ is not consulted).  The problem manifests as a generic 404 (because the request
is propagated to the underlying JspServlet which can not find these paths and jsps in the
war)

This is most notable in a basic solr install when clicking some URLs that are linked to from
the main admin page (see comments below) but this problem can also affect any situation where
a client is attempting to access a request handler (or "/select/") using a path ending in
"/".  The workaround is to remove hte trailing "/" character

  was:
Based on this thread, users seem to have problems with Solr on tomcat 7 that do not exist
on tomcat 6...

http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat



Updated description to clarify the scope of hte problem

> request handler paths ending in "/" don't work with Tomcat 7
> ------------------------------------------------------------
>
>                 Key: SOLR-2022
>                 URL: https://issues.apache.org/jira/browse/SOLR-2022
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 1.1.0, 1.2, 1.3, 1.4, 1.4.1, 1.4.2, 1.5, 3.1, 4.0, Next
>            Reporter: Hoss Man
>
> As originally reported in this thread...
> http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
> Tomcat 7 has made changes in how URLs are resolved that result in the requests with paths
that end in a "/" character being given to the SolrDispatchFilter  with "index.jsp" appended
to them.  This results in SolrDispatchFilter being unable to correctly identify some situations
when a request should be processed by a request handler based on the name registered (ie:
"/update/csv/" is seen as "update/csv/index.jsp" so as a result the handler registered to
"/update/csv/ is not consulted).  The problem manifests as a generic 404 (because the request
is propagated to the underlying JspServlet which can not find these paths and jsps in the
war)
> This is most notable in a basic solr install when clicking some URLs that are linked
to from the main admin page (see comments below) but this problem can also affect any situation
where a client is attempting to access a request handler (or "/select/") using a path ending
in "/".  The workaround is to remove hte trailing "/" character

-- 
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message