Hi!

The path to the aggregated javascript included on the page by T5 looks like
this:

/assets/virtual/
H4sIAAAAAAAAAJXQUWrDMAyAYTPY065RyhjUTrdlawc9S3AcOVOb2MZSRtMz7Wq7w$002bJAAn1J6ZsR3y8b$002f$002f6Jx4sQD1II8SRelCYCJkUmYmBtusZ3pHK5lZnMVYiePfcB5JGEXLZX0$002bSflz1YC4ZHuZok6wDEsZ$002fRNEhqPamy0eZUYqxmNk$002bS29zctmmBSNcwXv41cR2CejfG7t8$002bqizf63L3OvxAYupIypygQvZxPqT2877WeGexTuFuMTS$002bDd6B47GGH4g9f6Mby8MdJUJwtcVzwdhAWd9$002bcYtndKQuw4qiC5VmiMW2yIbwH4zpiYQ3AgAA.js

This causes problems on some appservers. Specifically, JK connector for IIS
chokes on this and won't deliver the scripts to the client, due to the very
long url. We had to turn off script combination for this customer.

Is it possible to use a shorter url? I realize that there probably is a
reason for this url, but does it REALLY have to be THAT long? :)

Reply via email to