New subject: [Bug 39637] Patron search generates URIs that are too long and can cause "HTTP 414 URI Too Long" errors

15 Apr 2025

      https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39637

            Bug ID: 39637
           Summary: Patron search generates URIs that are too long and can
                    cause "HTTP 414 URI Too Long" errors
 Change sponsored?: ---
           Product: Koha
           Version: Main
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: Patrons
          Assignee: koha-bugs@lists.koha-community.org
          Reporter: julian.maurice@biblibre.com
        QA Contact: testopia@bugs.koha-community.org
                CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com

Continuation of bug 31104 which did not solve the problem completely.

Steps to reproduce:
1. Log in to staff interface
2. In the top search bar, select "Patrons search" and type "a b c d e f g h i j
k l m" and submit the form
3. The patrons table should fail to load with a message like this: "Something
went wrong when loading the table. 414: Request-URI Too Long.". If the table
loads successfully, try adding a few more letters (separated by space) to the
search.

Another error that can happen is a 5XX error caused by the length of Link
headers.

Here is the (decoded) URL generated for "a b c d e":
http://koha-dev-main/api/v1/patrons?_page=1&_per_page=20&q=[{"-and":[[{"me.firstname":{"like":"a%"}},{"me.preferred_name":{"like":"a%"}},{"me.middle_name":{"like":"a%"}},{"me.surname":{"like":"a%"}},{"me.othernames":{"like":"a%"}},{"me.cardnumber":{"like":"a%"}},{"me.userid":{"like":"a%"}}],[{"me.firstname":{"like":"b%"}},{"me.preferred_name":{"like":"b%"}},{"me.middle_name":{"like":"b%"}},{"me.surname":{"like":"b%"}},{"me.othernames":{"like":"b%"}},{"me.cardnumber":{"like":"b%"}},{"me.userid":{"like":"b%"}}],[{"me.firstname":{"like":"c%"}},{"me.preferred_name":{"like":"c%"}},{"me.middle_name":{"like":"c%"}},{"me.surname":{"like":"c%"}},{"me.othernames":{"like":"c%"}},{"me.cardnumber":{"like":"c%"}},{"me.userid":{"like":"c%"}}],[{"me.firstname":{"like":"d%"}},{"me.preferred_name":{"like":"d%"}},{"me.middle_name":{"like":"d%"}},{"me.surname":{"like":"d%"}},{"me.othernames":{"like":"d%"}},{"me.cardnumber":{"like":"d%"}},{"me.userid":{"like":"d%"}}],[{"me.firstname":{"like":"e%"}},{"me.preferred_name":{"like":"e%"}},{"me.middle_name":{"like":"e%"}},{"me.surname":{"like":"e%"}},{"me.othernames":{"like":"e%"}},{"me.cardnumber":{"like":"e%"}},{"me.userid":{"like":"e%"}}]]},{"-or":[{"me.firstname":{"like":"a+b+c+d+e%"}},{"me.preferred_name":{"like":"a+b+c+d+e%"}},{"me.middle_name":{"like":"a+b+c+d+e%"}},{"me.surname":{"like":"a+b+c+d+e%"}},{"me.othernames":{"like":"a+b+c+d+e%"}},{"me.cardnumber":{"like":"a+b+c+d+e%"}},{"me.userid":{"like":"a+b+c+d+e%"}}]},{"-and":[[{"extended_attributes.value":{"like":"a%"},"extended_attributes.code":[["Nickname","PAT_1"]]}],[{"extended_attributes.value":{"like":"b%"},"extended_attributes.code":[["Nickname","PAT_1"]]}],[{"extended_attributes.value":{"like":"c%"},"extended_attributes.code":[["Nickname","PAT_1"]]}],[{"extended_attributes.value":{"like":"d%"},"extended_attributes.code":[["Nickname","PAT_1"]]}],[{"extended_attributes.value":{"like":"e%"},"extended_attributes.code":[["Nickname","PAT_1"]]}]]}]&_match=contains&_order_by=+me.surname,+me.preferred_name,+me.firstname,+me.middle_name,+me.othernames,+me.street_number,+me.address,+me.address2,+me.city,+me.state,+me.postal_code,+me.country

(Ignore the extended_attributes.* params that are not the main issue here, even
though they contribute to the problem)

If I'm counting correctly, for each word searched, the URL length is increased
by (216 + 7 * <word length>) characters (before encoding, which also increases
the URI length by a lot).
For me, with Apache, the problem happens around 8k characters (after encoding).

IMO it would be better to send only parameters like 'search', 'search_type' and
'search_field' to the API and translate this to DBIC dialect on the backend.
This would make it a lot harder to reach the limit (and would make the URI far
more readable, which is always nice :))

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.

[Bug 39637] New: Patron search generates URIs that are too long and can cause "HTTP 414 URI Too Long" errors

tags

participants (1)