After clearing all caches for the site http://www.yourarlington.com/, the site’s .css and template fails to load at first (in FF, Chrome and IE). Refreshing loads the sie – and any page cleared from the cache.
Using webpage test, you can see the .css and .js files that return 404s on initial site load:
http://www.webpagetest.org/performance_optimization.php?test=130823_G8_WQ8&run=1&cached=0
What can I do about this? :huh:
Thanks for your advice.
Bob Sprague
They are 403’s (not authorized), not 404’s. Are you requiring a cookie or session to access the static resources?
Thanks for clarifying. I don’t know how to do what you are suggesting, so I simply want to know: How do I prevent what is occurring?
Bob
You need to figure out why your server is rejecting the requests (look in your access and error logs). Something on the server is configured to require “something” (authenticated session, cookies, etc) for the resources and it is failing the requests that come in before that “something” is set.
If you didn’t configure or set up the app and server you may need to ping the person who did.
Thanks very much, Patrick. I’ll check the logs and inquire with my host.
Bob
[quote=“bob_sprague, post:5, topic:8322”]
I asked my host, Open Source Host, to investigate this issue. Support suggests its my browser and not the server. Can this really be? I see the problem no matter what browser I use.
Here is what support says:
"I am unable to recreate the issue at our end. The domain is loading fine from our end without any issue. I have also checked the domain after clearing the browser cache and couldn’t find any issue. Please refer the screenshot attached below. [none was attached; I asked for one.]
"This seems to be an issue on your browser. The issue you are facing is not related to the server.
“Your domain “yourarlington.com” is hosted in a shared server. We can’t tweak the server with the details mentioned in the above URL. It will affect the other customers in the server. You need to contact your developer and optimise the domain as per details mentioned in the URL mentioned above.”
I have explained the situation to my host, Open Source House, a number of times. In each case, support replies as it does here:
"Thanks for your update. From your reply it is seen that, there is some compatibility issues with the website files when accessing it via browser. Since we are unable to recreate the issue from our end we could not investigate the issue further.
“However, there is no issue from the server and we are unable to support on this issue further. Sorry for the inconvenience. Please check whether any file is not compatible with the browser and if so you can optimize it accordingly.”
In order words, the host says it is not a server issue, but a browser issue. They claim this even though three browsers return the same errors to me – as well as a number of my readers (see initial post).
Is my host passing the buck? If so, how might I proceed?
Bob Sprague
It partially sounds like they have no idea what they are doing but depending on what the host is responsible for it may not be their issue. The problem may be in a .htaccess rule or with the site code itself.
Do you have access to the web error log on the server? That should list some messages about why the 403’s are being generated.
Yes, I have access to the error and access logs. I have not been able to track down specific causes for the 403s. Most host, which looked at logs to which I don’t have access, could find nothing either. They continue to say their servers are fine and that it’s likely a code issue on my site, and they don’t deal with that. The behavior continues, and I do not know the cause. Thank you for your help in the matter.
Bob Sprague
I believe you should ask folks at Artisteer, thy should know right away what may be the cause of your problem.