Kunwar, have you had a chance to look at this?

Kunwar, have you had a chance to look at this?

I was thinking the unicode literal encoding was helping, but I later found that it was doing some weird String conversions and ended up just turning the unicode characters to question marks, so it really wasn't helping like I thought it was.This particular search seems to break AEM in mutliple ways....

That does seem to work better, but how would I achieve this without a String literal? This is input that is coming in from a http query parameter so I can't just use a String literal like that.

We are using AEM 6.3 SP1 and have cases where using SimpleSearch has brought down our AEM instances with one user doing a query with unicode characters. A simple example is something likeimport com.day.cq.search.SimpleSearch; import com.day.cq.search.Predicate; import com.day.cq.search.result.Search...

Thanks, all I had to do was allow the read permission for the anonymous user on for /libs/clientlibs/granite/jquery-ui/resources on the publish instances and it worked.

I'm trying to get the resource /libs/clientlibs/granite/jquery-ui/resources/ui-bg_glass_75_dadada_1x400.png to load on my publish AEM 6.3 instances but every time I get errors like8.05.2018 15:26:19.921 *INFO* [127.0.0.1 [1525811179908] GET /libs/clientlibs/granite/jquery-ui/resources/ui-bg_glass_75...

I guess I found out why this is happening, and it appears to be a bug with Apache 2.4 when Apache serves the file (like it would out of the dispatcher cache) it adds the ETag information with "-gzip" added to the end of the ETag. But it seems on the next request, the "-gzip" appended to the end make...

With Apache compressing the cached documents in the dispatcher, the ETag is set like:ETag: "796-56562d1294cfd-gzip"and Apache compression is enabled with:AddOutputFilterByType DEFLATE "image/svg+xml"But when it is compared against the cached file, it always returns a 200 instead of a 304.The dispatc...

I'm having a similar issue. I'm using Dispatcher 4.2.3 and caching the response headers, but when a cached dam asset is returned, the cached header value is not used, the last modified time of the actual cached file is still used. Any ideas? /clientheaders allows all headers.