Hello all, My name is Marco Afonso, I work for a local governament in Portugal. I'm comming here to report that we have Koha installed on our municipality library. Now our network team, activated Sophos WAF firewall, and some requestes are being blocked because of URL size when performing search on backoffice. For example, when using quick search, searching for only a name, let say, "Maria", it generates a long request to the server - see below: https://my.url/api/v1/patrons?_page=1&_per_page=20&q=%5B%7B%22-and%22%3A%5B%5B%7B%22me.borrowernumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.cardnumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.firstname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.middle_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.othernames%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.preferred_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.surname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.userid%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%5D%5D%7D%2C%7B%22-or%22%3A%5B%7B%22me.borrowernumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.cardnumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.firstname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.middle_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.othernames%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.preferred_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.surname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.userid%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%5D%7D%2C%7B%22-and%22%3A%5B%5B%7B%22extended_attributes.value%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%2C%22extended_attributes.code%22%3A%5B%5B%22CC%22%2C%22GEAM%22%2C%22GEX%22%2C%22NIF%22%2C%22NL%22%5D%5D%7D%5D%5D%7D%5D&_match=contains&_order_by=%2Bme.surname%2C%2Bme.preferred_name%2C%2Bme.firstname%2C%2Bme.middle_name%2C%2Bme.othernames%2C%2Bme.street_number%2C%2Bme.address%2C%2Bme.address2%2C%2Bme.city%2C%2Bme.state%2C%2Bme.postal_code%2C%2Bme.country I'm thinking in one alternative: 1 - could we change from GET request to POST ? changing in the frontend the HTTP metod, will the server process the request? Maybe this is something that could be considered. Anyway, let know what you think about it. Kind regards, Marco
Olá Marco, POST won't work: POST /api/v1/patrons creates a patron, it doesn't search. The long URL is expected. The staff interface sends search filters to the API as JSON in the URL, and other tables do the same, not just patron search. I believe the fix is to raise the WAF's URL length limit for */api/v1/* on the staff interface. Don't exclude the path entirely, so other protections remain active. You can also shorten the URL by removing unneeded fields from *DefaultPatronSearchFields* and/or unticking 'Search by default' on patron attribute types which staff don't need in quick search. That helps, but it won't guarantee staying under the limit. Regards, Pedro Amorim Software Engineer Open Fifth pedro.amorim@openfifth.co.uk www.openfifth.co.uk [image: Bsky social] <https://bsky.app/profile/openfifth.bsky.social> [image: LinkedIn] <https://www.linkedin.com/company/openfifth/> [image: YouTube] <https://www.youtube.com/@OpenFifthLimited> We launched Open Fifth on 26 March 2025. Learn more about our new name here <https://www.openfifth.co.uk/openfifth_docs/OpenFifthPressRelease.pdf>. On Thu, 19 Nov 2026 at 11:29, Marco Afonso via Koha-devel < koha-devel@lists.koha-community.org> wrote:
Hello all,
My name is Marco Afonso, I work for a local governament in Portugal.
I'm comming here to report that we have Koha installed on our municipality library.
Now our network team, activated Sophos WAF firewall, and some requestes are being blocked because of URL size when performing search on backoffice.
For example, when using quick search, searching for only a name, let say, "Maria", it generates a long request to the server - see below:
d_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.surname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.userid%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%5D%7D%2C%7B%22-and%22%3A%5B%5B%7B%22extended_attributes.value%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%2C%22extended_attributes.code%22%3A%5B%5B%22CC%22%2C%22GEAM%22%2C%22GEX%22%2C%22NIF%22%2C%22NL%22%5D%5D%7D%5D%5D%7D%5D&_match=contains&_order_by=%2Bme.surname%2C%2Bme.preferred_name%2C%2Bme.firstname%2C%2Bme.middle_name%2C%2Bme.othernames%2C%2Bme.street_number%2C%2Bme.address%2C%2Bme.address2%2C%2Bme.city%2C%2Bme.state%2C%2Bme.postal_code%2C%2Bme.country
I'm thinking in one alternative: 1 - could we change from GET request to POST ? changing in the frontend the HTTP metod, will the server process the request?
Maybe this is something that could be considered. Anyway, let know what you think about it.
Kind regards, Marco _______________________________________________ Koha-devel mailing list -- koha-devel@lists.koha-community.org To unsubscribe send an email to koha-devel-leave@lists.koha-community.org website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
Hi all, My hope is that one day we create a new endpoint for intranet member search that uses POST. Something like POST /api/v1/patrons/search perhaps. There might be a report on Bugzilla for that, but I imagine it's a long way from progressing still. David Cook Lead Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 -----Original Message----- From: Amorim, Pedro via Koha-devel <koha-devel@lists.koha-community.org> Sent: Thursday, 19 November 2026 11:51 PM To: Marco Afonso <mafonso@cm-tavira.pt> Cc: koha-devel@lists.koha-community.org Subject: [Koha-devel] Re: Intranet search member generates long GET request Olá Marco, POST won't work: POST /api/v1/patrons creates a patron, it doesn't search. The long URL is expected. The staff interface sends search filters to the API as JSON in the URL, and other tables do the same, not just patron search. I believe the fix is to raise the WAF's URL length limit for /api/v1/ on the staff interface. Don't exclude the path entirely, so other protections remain active. You can also shorten the URL by removing unneeded fields from DefaultPatronSearchFields and/or unticking 'Search by default' on patron attribute types which staff don't need in quick search. That helps, but it won't guarantee staying under the limit. Regards, Pedro Amorim Software Engineer Open Fifth <https://lh7-rt.googleusercontent.com/docsz/AD_4nXfoUG8s__F4xPiMmjniWwOV2OtkPbRKeUClS60uwCXsU0yTJlXU2CWuUjyiWns_71idnjs12jlgFrkuIDoThPWmVuH0JTVJgSaPSNXNiln_ev1xPJABMCUrmG0VJVPYsG5HAGI7nFgBVv7rvAFT42o?key=RyiAVxoi7zwTRHuUFQ6-5AEh> pedro.amorim@openfifth.co.uk <mailto:pedro.amorim@openfifth.co.uk> <https://lh7-rt.googleusercontent.com/docsz/AD_4nXfX3ao_QmoQTRO2tNRZnKYMw9v3yE3TR7QteQhyNqhD8qCsqGcdiDeM7L6TF1Z1KpHhnEcK4ROvTMGsTwWJoQkYEQoisZNzp7wRcrDo1ctQTW1oYlnF8kpnDBzVFB3fG1YVHO8Y5w-Bm_Cr-_hXNxg?key=RyiAVxoi7zwTRHuUFQ6-5AEh> www.openfifth.co.uk <http://www.openfifth.co.uk> <https://bsky.app/profile/openfifth.bsky.social> <https://www.linkedin.com/company/openfifth/> <https://www.youtube.com/@OpenFifthLimited> <https://lh7-rt.googleusercontent.com/docsz/AD_4nXctzjIuPWiNeBqxFuVW3mj1dpuYHfhx5P95tgDcnNwuvFK6y_gcXK_XLDIe-NDI6lPFvz4t6v-FT_gfed-I8aEUn7lBlGFUyj3u3pEy8_m2EkPBpwViMpHW3B9npEpb8lK2pNd_54wmRPfvqTs2sw?key=RyiAVxoi7zwTRHuUFQ6-5AEh> We launched Open Fifth on 26 March 2025. Learn more about our new name here <https://www.openfifth.co.uk/openfifth_docs/OpenFifthPressRelease.pdf> . On Thu, 19 Nov 2026 at 11:29, Marco Afonso via Koha-devel <koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> > wrote: Hello all, My name is Marco Afonso, I work for a local governament in Portugal. I'm comming here to report that we have Koha installed on our municipality library. Now our network team, activated Sophos WAF firewall, and some requestes are being blocked because of URL size when performing search on backoffice. For example, when using quick search, searching for only a name, let say, "Maria", it generates a long request to the server - see below: https://my.url/api/v1/patrons?_page=1&_per_page=20&q=%5B%7B%22-and%22%3A%5B%5B%7B%22me.borrowernumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.cardnumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.firstname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.middle_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.othernames%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.preferred_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.surname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.userid%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%5D%5D%7D%2C%7B%22-or%22%3A%5B%7B%22me.borrowernumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.cardnumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.firstname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.middle_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.othernames%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.preferre d_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.surname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.userid%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%5D%7D%2C%7B%22-and%22%3A%5B%5B%7B%22extended_attributes.value%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%2C%22extended_attributes.code%22%3A%5B%5B%22CC%22%2C%22GEAM%22%2C%22GEX%22%2C%22NIF%22%2C%22NL%22%5D%5D%7D%5D%5D%7D%5D&_match=contains&_order_by=%2Bme.surname%2C%2Bme.preferred_name%2C%2Bme.firstname%2C%2Bme.middle_name%2C%2Bme.othernames%2C%2Bme.street_number%2C%2Bme.address%2C%2Bme.address2%2C%2Bme.city%2C%2Bme.state%2C%2Bme.postal_code%2C%2Bme.country I'm thinking in one alternative: 1 - could we change from GET request to POST ? changing in the frontend the HTTP metod, will the server process the request? Maybe this is something that could be considered. Anyway, let know what you think about it. Kind regards, Marco _______________________________________________ Koha-devel mailing list -- koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> To unsubscribe send an email to koha-devel-leave@lists.koha-community.org <mailto:koha-devel-leave@lists.koha-community.org> website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
Hi, Have a look at Bug 39637 : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39637 Patron search generates URIs that are too long and can cause "HTTP 414 URI Too Long" errors Regards Le 20/11/2026 à 07:11, David Cook via Koha-devel a écrit :
Hi all,
My hope is that one day we create a new endpoint for intranet member search that uses POST. Something like POST /api/v1/patrons/search perhaps.
There might be a report on Bugzilla for that, but I imagine it's a long way from progressing still.
David Cook Lead Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia
Office: 02 9212 0899
-----Original Message----- From: Amorim, Pedro via Koha-devel <koha-devel@lists.koha-community.org> Sent: Thursday, 19 November 2026 11:51 PM To: Marco Afonso <mafonso@cm-tavira.pt> Cc: koha-devel@lists.koha-community.org Subject: [Koha-devel] Re: Intranet search member generates long GET request
Olá Marco,
POST won't work: POST /api/v1/patrons creates a patron, it doesn't search. The long URL is expected. The staff interface sends search filters to the API as JSON in the URL, and other tables do the same, not just patron search. I believe the fix is to raise the WAF's URL length limit for /api/v1/ on the staff interface. Don't exclude the path entirely, so other protections remain active.
You can also shorten the URL by removing unneeded fields from DefaultPatronSearchFields and/or unticking 'Search by default' on patron attribute types which staff don't need in quick search. That helps, but it won't guarantee staying under the limit.
Regards,
Pedro Amorim
Software Engineer
Open Fifth
<https://lh7-rt.googleusercontent.com/docsz/AD_4nXfoUG8s__F4xPiMmjniWwOV2OtkPbRKeUClS60uwCXsU0yTJlXU2CWuUjyiWns_71idnjs12jlgFrkuIDoThPWmVuH0JTVJgSaPSNXNiln_ev1xPJABMCUrmG0VJVPYsG5HAGI7nFgBVv7rvAFT42o?key=RyiAVxoi7zwTRHuUFQ6-5AEh> pedro.amorim@openfifth.co.uk <mailto:pedro.amorim@openfifth.co.uk>
<https://lh7-rt.googleusercontent.com/docsz/AD_4nXfX3ao_QmoQTRO2tNRZnKYMw9v3yE3TR7QteQhyNqhD8qCsqGcdiDeM7L6TF1Z1KpHhnEcK4ROvTMGsTwWJoQkYEQoisZNzp7wRcrDo1ctQTW1oYlnF8kpnDBzVFB3fG1YVHO8Y5w-Bm_Cr-_hXNxg?key=RyiAVxoi7zwTRHuUFQ6-5AEh> www.openfifth.co.uk <http://www.openfifth.co.uk>
<https://bsky.app/profile/openfifth.bsky.social> <https://www.linkedin.com/company/openfifth/> <https://www.youtube.com/@OpenFifthLimited>
We launched Open Fifth on 26 March 2025. Learn more about our new name here <https://www.openfifth.co.uk/openfifth_docs/OpenFifthPressRelease.pdf> .
On Thu, 19 Nov 2026 at 11:29, Marco Afonso via Koha-devel <koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> > wrote:
Hello all,
My name is Marco Afonso, I work for a local governament in Portugal.
I'm comming here to report that we have Koha installed on our municipality library.
Now our network team, activated Sophos WAF firewall, and some requestes are being blocked because of URL size when performing search on backoffice.
For example, when using quick search, searching for only a name, let say, "Maria", it generates a long request to the server - see below:
https://my.url/api/v1/patrons?_page=1&_per_page=20&q=%5B%7B%22-and%22%3A%5B%5B%7B%22me.borrowernumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.cardnumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.firstname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.middle_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.othernames%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.preferred_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.surname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.userid%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%5D%5D%7D%2C%7B%22-or%22%3A%5B%7B%22me.borrowernumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.cardnumber%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.firstname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.middle_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.othernames%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.preferre d_name%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.surname%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%2C%7B%22me.userid%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%7D%5D%7D%2C%7B%22-and%22%3A%5B%5B%7B%22extended_attributes.value%22%3A%7B%22like%22%3A%22%25Maria%25%22%7D%2C%22extended_attributes.code%22%3A%5B%5B%22CC%22%2C%22GEAM%22%2C%22GEX%22%2C%22NIF%22%2C%22NL%22%5D%5D%7D%5D%5D%7D%5D&_match=contains&_order_by=%2Bme.surname%2C%2Bme.preferred_name%2C%2Bme.firstname%2C%2Bme.middle_name%2C%2Bme.othernames%2C%2Bme.street_number%2C%2Bme.address%2C%2Bme.address2%2C%2Bme.city%2C%2Bme.state%2C%2Bme.postal_code%2C%2Bme.country
I'm thinking in one alternative: 1 - could we change from GET request to POST ? changing in the frontend the HTTP metod, will the server process the request?
Maybe this is something that could be considered. Anyway, let know what you think about it.
Kind regards, Marco _______________________________________________ Koha-devel mailing list -- koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> To unsubscribe send an email to koha-devel-leave@lists.koha-community.org <mailto:koha-devel-leave@lists.koha-community.org> website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list -- koha-devel@lists.koha-community.org To unsubscribe send an email to koha-devel-leave@lists.koha-community.org website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
-- Fridolin SOMERS <fridolin.somers@biblibre.com> Software and system maintainer 🦄 BibLibre, France
participants (4)
-
Amorim, Pedro -
David Cook -
Fridolin SOMERS -
Marco Afonso