https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32401 --- Comment #2 from David Cook <dcook@prosentient.com.au> --- Ah, the problem is "x-koha-query". It looks like browsers don't like headers with non ISO-8859-1 values: "{"-and":[{"basket.vendor_id":46},[[{"basket.name":{"like":"%خمسة%"}}],[{"basket.basket_group.name":{"like":"%خمسة%"}}],[{"me.order_id":{"like":"%خمسة%"}}],[{"biblio.title":{"like":"%خمسة%"}},{"biblio.author":{"like":"%خمسة%"}},{"biblio.isbn":{"like":"%خمسة%"}},{"biblio.publisher":{"like":"%خمسة%"}},{"me.internal_note":{"like":"%خمسة%"}},{"me.vendor_note":{"like":"%خمسة%"}}],[{"me.replacement_price":{"like":"%خمسة%"}}],[{"me.quantity":{"like":"%خمسة%"}}],[{"me.ecost":{"like":"%خمسة%"}}],[{"fund.name":{"like":"%خمسة%"}}]]]}" According to https://www.rfc-editor.org/rfc/rfc7230#section-3.2.4 Historically, HTTP has allowed field content with text in the ISO-8859-1 charset [ISO-8859-1], supporting other charsets only through use of [RFC2047] encoding. In practice, most HTTP header field values use only a subset of the US-ASCII charset [USASCII]. Newly defined header fields SHOULD limit their field values to US-ASCII octets. A recipient SHOULD treat other octets in field content (obs-text) as opaque data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.