I'm getting a 403 error, a forbidden access error on some pages after I have added AdSense to my website. Error sometimes happens to one page, sometimes to other ones, but it has something to do with the sessions ie. the same pages are/are not working in the same browser session. Everything was working perfectly before adding AdSense.
The server used is LiteSpeed.
Related
When I try to access a page on my IIS web I get an error 403. The error is not logged to the log file and the error page shown is not the one that's defined in the config.
That's the content of the error page:
<html><head><title>403 Forbidden</title></head><body>Access denied</body>
Can anyone help me to find this error page and get the error logged?
The 403 Forbidden error is an HTTP status code that means that accessing the page or directory you were trying to reach is absolutely forbidden for some reason.
To resolve this issue, you need to enable directory browsing for your application. To enable directory browsing on IIS, check out the steps from this Microsoft document.
If you still can’t solve the problem, you can use failed request tracking to view detailed error information.
I have a situation here, on iis logs I see the /CMSPages/PortalTemplate.aspx causing 404 errors but the requests are still fulfilled.
The question that I have is how do I stop these 404 errors from being logged since the website still works. I only want to see the real 404 erros which occur when the request URL is invalid
I am using the Portal Engine approach
In the IIS log, find out what the parameters after the /CMSPages/PortalTemplate.aspx causing the 404. You may be able to see these 404 errors in the Kentico Event Log as well. The majority of the requests to deliver page content goes through the /CMSPages/PortalTemplate.aspx page which is why you're seeing it in the IIS logs.
Once you find the record which has the 404 info, you should be able to find the path to the file and resolve it.
Check your network tab in your favorite browser. Usually there is a favicon or woff font not being served.
I have a classic asp web application in which I've created a custom friendly 404 page. Also within that page, I have logic to email me the 404 info so I can check it out as to why it happened.
One of the pieces of info I email to myself is
Request.ServerVariables("HTTP_REFERER")
As I understand it, it should tell me the origin of the 404, ie. the page which is making the request to the file that doesn't exist.
However, I get notifications where the Referer is referencing a page in my site that doesn't exist in the first place. How can this be? Am I pulling the wrong ServerVariable? Is someone trying to do some cross site scripting?
IIS 6.1 - Custom Error pages.
The web site is defined as www.url.com/mysite. Custom error pages have been defined for mysite. 404 and 500.100.
I can redirect to /mysite/500.htm and /mysite/400.htm.
I can set 500.100 to redirect to /global/500.htm and this works.
When I redirect 404 to /global/404.htm I get a 403 access denied error. (I also tried redirecting 404 to /global/500.htm just to make sure it was not file-specific rights.)
Directory browsing is enabled.
The page works if you browse directly to it.
Checked the iis log file for oddities.
Can anyone offer an explanation that might lead me in the right direction?
My website is accessible without www in the front of it in Firefox and Safari however for some reason it is not in Chrome. Is there anything that I need to change on my website host or in the html to make it accessible?
If your website is not already set up to do so, you'll need to update your web host to respect requests for http://your-website.com as well as http://www.your-website.com.
Firefox (and apparently Safari) will make a second request to a URL using or removing the www. in front of it if they receive a 404 error before displaying any resulting errors to the user. (And if the alternate URL works they will display the results of the second request and silently drop the results of the first [the 404 error].) Most, if not all other browsers will just display the first 404 error page.
What web server are you running on?