Too long filenames ending with .q.js ?
-
He Albert,
I’ve been having errors in the php log recarding too long filenames and I’m wondering if it has something to do with PhastPress. I see that phastpress generates very long filenames ending on .q.js and the filenames that have been reported as being too long have such names. Can it be that the filenames you generate cause these kinds of errors?
A reason why I have some doubt is that the files don’t have phastpress in their names, they are sought in the website root and they don’t seem to exist either. But given that I only know phastpress to use such filenames in the URLs, I hope it might be related.
[core:error] [pid 23925] (36)File name too long: [client 66.249.66.5:46824] AH00036: access to /c2VydmljZT1idW5kbGVyJnI9LVRmU3cycW5XUkkmcj0yeUlpWG1KbzF1ZyZyPTNYd0tHMkFXVGhRJnI9NzVudVZKMVhVWTQmcj03OGNybGl6MGF2OCZyPUFOdTZUQl9GbWNvJnI9QWNjS2c1T3IwY0kmcj1DYnF0bmF3eTZDdyZyPVNfb3ZLMDllcXBrJnI9X1ZUVkZvMFJVT2Mmcj1kc05CY2JSX2pucyZyPWhYVjlSTnZjRjFZJnI9ajluTXFkNGZvbE0mcj1weWVQOWtueTRGNCZyPXJpX2pSUmFxcXVrJnI9d2o1ek4tbGZtd1Umcj14LXh0eWE2Y1paUSZyPXlUQXhHU0JsQnhJ.q.js failed (filesystem path '/home/460400.cloudwaysapps.com/txyuuwbbzk/public_html/c2VydmljZT1idW5kbGVyJnI9LVRmU3cycW5XUkkmcj0yeUlpWG1KbzF1ZyZyPTNYd0tHMkFXVGhRJnI9NzVudVZKMVhVWTQmcj03OGNybGl6MGF2OCZyPUFOdTZUQl9GbWNvJnI9QWNjS2c1T3IwY0kmcj1DYnF0bmF3eTZDdyZyPVNfb3ZLMDllcXBrJnI9X1ZUVkZvMFJVT2Mmcj1kc05CY2JSX2pucyZyPWhYVjlSTnZjRjFZJnI9ajluTXFkNGZvbE0mcj1weWVQOWtueTRGNCZyPXJpX2pSUmFxcXVrJnI9d2o1ek4tbGZtd1Umcj14LXh0eWE2Y1paUSZyPXlUQXhHU0JsQnhJ.q.js'), referer: https://dewitteprins.nl/opgroeien-emoties-en-de-ziel/
Strangely enough all functionality seems to work on my website, so this issue doesn’t seem to block anything, but I was surprised to see the length of the filenames too.
When I test a page using gt-metrix I see such long filenames with an url that starts with
https://dewitteprins.nl/wp-content/plugins/phastpress/phast.php/
https://dewitteprins.nl/wp-content/plugins/phastpress/phast.php/c2VydmljZT1idW5kbGVyJnI9LTRFTWIwOEp3b2Mmcj0tNVlmNWpqcUtaRSZyPTB1bXNnRTE5Mk1RJnI9MnZKbHp6eUtmWjgmcj0ydmFpVE1mZm5NRSZyPTNadG5QczlKOWdJJnI9M2hkLV9yTUtsU28mcj01OFNVUE1ib0VaTSZyPTVDM3lUUUxHVWw4JnI9OG0ycDFzLTVyNlUmcj05OGxpSEotekFzcyZyPUFWWG9PTndoRHVJJnI9QWdDMlZOUzhXZG8mcj1BckV1Sl93b3hzcyZyPUF0eW1naGpGN3EwJnI9QnhXZXRoOGctX1Umcj1DVTc0a2hfWkFOQSZyPURnSGJNbm5FVnhrJnI9RVdhNjRKNDc4TFkmcj1FY0RXMEtXTlZIdyZyPUZGYi12X1EyYVp3JnI9RzZOcEpnYUpWV28mcj1HdTBBQVdCNndSUSZyPUg4M1JNc0FKbjQwJnI9SEFiQlE5eGRWS1kmcj1JRTRQc21mM0JaUSZyPUtIMl9WYnBkSHJzJnI9TE81QWJFbGRlNHcmcj1MVm5DTnJTRHYzYyZyPUxrUHNnZlQweTdzJnI9THRhaUYtWTVGWFEmcj1MdG80VGlSS25fcyZyPU10bE5sSVN6TmtrJnI9Tk9JZ0VRb2l4c0kmcj1PMUpvczU4M3pZMCZyPU9kbl9RMVpCcjNVJnI9T3BXc19FUVhZS00mcj1QTFRPclVyYldMVSZyPVBNQ3d5QWpuXzZFJnI9UHZlR0ZQQm9ucncmcj1QeEg4Yy0xMmhrTSZyPVFoTi11SDZTY0p3JnI9UXQ0bEh0MzUtdG8mcj1SZnN4cXpmdXVlMCZyPVNHbG0zXzFOQTVJJnI9VDhOdGt1cTlMbk0mcj1UZWc4TjJFZFZ0ayZyPVdxWURjRE9fZ0hJJnI9WERNZ0o5cHpPQW8mcj1YRG5OR3pQRE9wQSZyPVhLRzdOUFh6NFJzJnI9WGJLeS10NC03MWsmcj1ZRnpSbngtTnFKZyZyPVlHRGNHc2txeHBrJnI9WjNiUTNCVzc2TU0mcj1aUE1LQW1tYzFYQSZyPV9DNnQzamljRWU0JnI9X1FsNDNoNDk2U1Umcj1hNXdyUlR1VzJNZyZyPWI3TjdwN0NuYnB3JnI9Y0J1YndWeHZFbjAmcj1lOUZEVk5FTmc0SSZyPWVFeEZVdXpNcnc0JnI9ZWE4SFhvUnZfM1kmcj1lc2s2T0k1SW9KcyZyPWZJRkFFRThjeDFVJnI9Zmt6aFptMF9JbG8mcj1mbXd2b3Y1eG9XOCZyPWh1STBJeGtSWTNFJnI9aVlNMF9HV1hLaUEmcj1qcFM4ZUdoSVM1byZyPWswNDNQemVZOV9VJnI9azZIbi1IUGoxOG8mcj1rZURwMnp0ekZxQSZyPWtqcndNdnY3S05FJnI9bEdtYWtCc0FaSkEmcj1sd1p2VTZBQlhTYyZyPW1HM1N0bk1SVG5NJnI9bjBmXzhJWWZKRG8mcj1uNWV0ZnJ0enZYWSZyPW5GeEtaSV9paDVvJnI9cEs5WDNXRUMySE0mcj1wdnlfM3QtRG9zYyZyPXMyWE5FbjdxMkE4JnI9c1dzblF1WWVhOXcmcj1zZ1p6N1ZMQUJkWSZyPXRGLThfZWp3eF9BJnI9dE5YLVJQTGVVMEEmcj11TXhKNXJVSEJpNCZyPXVvLTZ2Ni1NSEdrJnI9djlNcEpGQm9ocVUmcj12TzRkR2pJdVRtMCZyPXZZRjVOcmRxY3BrJnI9d1I5dmNlc2hpWmMmcj13X1pNWVg5eDdTSSZyPXlHTGVpSGI2ZnI0.q.js
There it reports they are missing a cache validator. “Resources that do not specify a cache validator cannot be refreshed efficiently. Specify a Last-Modified or ETag header to enable cache validation for the following resources.”
Is either familiar to you and can you perhaps offer some guidance in what to do?
Thanks,
Hans
- The topic ‘Too long filenames ending with .q.js ?’ is closed to new replies.