[jira] Created: (SOLR-2262) 404 on

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (SOLR-2262) 404 on

JIRA jira@apache.org
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-2262) 404 on

JIRA jira@apache.org

    [ 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Issue Comment Edited: (SOLR-2262) 404 on

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966603#action_12966603 ]

Fuad Efendi edited comment on SOLR-2262 at 12/3/10 1:01 PM:
------------------------------------------------------------

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}



      was (Author: funtick):
    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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-2262) 404 on

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966605#action_12966605 ]

Fuad Efendi commented on SOLR-2262:
-----------------------------------

Oh sorry!

It seems *Tomcat 6 had a bug* and Tomcat 7 fixed that...
http://localhost:8080/solr/admin/file/
Solr core will put in a map "file" as a key, and ShowFileRequestHandler as a value, and will try to find handler using "file/" (Tomcat 7), or "file" (bug in Tomcat 6, so that it works)

Of course I'll test getPathInfo() for both...

> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (SOLR-2262) 404 on

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966609#action_12966609 ]

Fuad Efendi commented on SOLR-2262:
-----------------------------------

As a workaround for different containers, you can explicitly define
{code}
  <requestHandler name="/admin/file/"       class="org.apache.solr.handler.admin.ShowFileRequestHandler" >
{code}

(additionally to default "/admin/file")



We can also:
1. Use "startWith" instead of full String comparison
2. Use "longest match" to find registered request handler

(see SolrCore.getRequestHandler(String handlerName))


> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (SOLR-2262) 404 on

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Hoss Man resolved SOLR-2262.
----------------------------

    Resolution: Duplicate

Dup of SOLR-2022

> 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: [hidden email]
For additional commands, e-mail: [hidden email]