Solr
  1. Solr
  2. SOLR-70

ping.jsp is very naive -- doesn't work with "qt" or any extra query args

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0
    • Component/s: None
    • Labels:
      None

      Description

      while reviewing SOLR-58 i noticed that ping.jsp is extremely naive about the types of requests it can use to sanity check the index, in particular:

      • it treats the first query param that starts with "q" as the query string (like for example "qt")
      • it ignores all other query params

      ...this makes it worthless to try and configure anything but the standard querest handler with no options as your ping URL.

        Activity

        Hide
        Hoss Man added a comment -

        improvement of the parsing, along with a comment in the example solrconfig.xml about exactly what kind of string should be in <pingQuery>

        ...fixed the issue where all params were ignored, and the first param that started with a "q" was used as a query ("qt" for example) but didn't try to change the format, or add any url-unescaping.

        Show
        Hoss Man added a comment - improvement of the parsing, along with a comment in the example solrconfig.xml about exactly what kind of string should be in <pingQuery> ...fixed the issue where all params were ignored, and the first param that started with a "q" was used as a query ("qt" for example) but didn't try to change the format, or add any url-unescaping.
        Hide
        Hoss Man added a comment -

        commited variation of patch which worked against trunk (with newer XML based pages)

        Show
        Hoss Man added a comment - commited variation of patch which worked against trunk (with newer XML based pages)
        Hide
        Hoss Man added a comment -

        This bug was modified as part of a bulk update using the criteria...

        • Marked ("Resolved" or "Closed") and "Fixed"
        • Had no "Fix Version" versions
        • Was listed in the CHANGES.txt for 1.1

        The Fix Version for all 38 issues found was set to 1.1, email notification
        was suppressed to prevent excessive email.

        For a list of all the issues modified, search jira comments for this
        (hopefully) unique string: 20080415hossman3

        Show
        Hoss Man added a comment - This bug was modified as part of a bulk update using the criteria... Marked ("Resolved" or "Closed") and "Fixed" Had no "Fix Version" versions Was listed in the CHANGES.txt for 1.1 The Fix Version for all 38 issues found was set to 1.1, email notification was suppressed to prevent excessive email. For a list of all the issues modified, search jira comments for this (hopefully) unique string: 20080415hossman3

          People

          • Assignee:
            Hoss Man
            Reporter:
            Hoss Man
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development