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

Upayavira commented on SOLR-10037:
----------------------------------

There is a ticket that takes the /solr out of URLs used in the services.js 
file, making them relative such that Solr might be deployed to a different URL. 
It looks like this might be an inadvertent consequence of that change. See 
SOLR-9584.

> (non-original) Solr Admin UI > query tab > unexpected url above results
> -----------------------------------------------------------------------
>
>                 Key: SOLR-10037
>                 URL: https://issues.apache.org/jira/browse/SOLR-10037
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Christine Poerschke
>            Priority: Minor
>
> To reproduce, in a browser run a search from the query tab and then notice 
> the url shown above the results
> {code}
> # actual:   http://localhost:8983techproducts/select?indent=on&q=*:*&wt=json
> # expected: 
> http://localhost:8983/solr/techproducts/select?q=*%3A*&wt=json&indent=true
> {code}
> (We had noticed this when using the (master branch) Admin UI during the 
> [London Lucene Hackday for Full 
> Fact|https://www.meetup.com/Apache-Lucene-Solr-London-User-Group/events/236356241/]
>  on Friday, I just tried to reproduce both on master (reproducible with 
> non-original version only) and on branch_6_4 (not reproducible) and search 
> for an existing open issue found no apparent match.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to