You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Uwe Schindler (Jira)" <ji...@apache.org> on 2019/11/18 16:52:00 UTC

[jira] [Commented] (SOLR-13941) Tests configure Jetty differently than when running via start.jar

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

Uwe Schindler commented on SOLR-13941:
--------------------------------------

OK, I see. I will check the test setup code to see how it binds the servlet/servletfilter and how the context path is setup.

> Tests configure Jetty differently than when running via start.jar
> -----------------------------------------------------------------
>
>                 Key: SOLR-13941
>                 URL: https://issues.apache.org/jira/browse/SOLR-13941
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Jan Høydahl
>            Assignee: Uwe Schindler
>            Priority: Major
>
> Spinoff from SOLR-13905.
> There seems to be a slightly different configuration of our servlets when Solr is run from command line and through Test-runner for our tests.
> This causes different behavior of {{httpRequest.getPathInfo}} and {{httpRequest.getServletPath()}} in the two environments, making it hard to depend on these in critical code paths, such as [SolrDispatchFilter|https://github.com/apache/lucene-solr/blob/f07998fc234c81ff956a84ee508b85f8d573ef38/solr/core/src/java/org/apache/solr/servlet/SolrDispatchFilter.java#L494-L499] and AuditEvent.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org