• I am new to WordPress. I am trying to set-up a site that is mostly static (80%), with a few focussed blogs.

    As there will be several static pages, and for SEO reasons I would like to use pretty permalinks. But when I try to set-up permalinks, adding a .htaccess file as per instructions, access to the site is blocked from some machines. I get the following message:

    “Access Denied (content_filter_denied). Your request was denied because of its content categorization: Blogs/Personal Pages”. This is a message produced by Blue Coat Web Filters.

    With the default (?p=123) permalinks selected I can access the site fine. Preferably, I would like to use PostName, but when sellecting this the site is blocked by Blue Coat.

    Is there a setting that I can change in the .htaccess or someother addin that allows for pretty permalinks that are not blocked by Web Filters?

    Any advice welcome.

Viewing 3 replies - 1 through 3 (of 3 total)
  • That message is not coming from WordPress. You need to contact your hosts about it.

    Thread Starter dsewell

    (@dsewell)

    Many thanks for your quick reply esmi. Absolutelly, I agree. This is not a WordPress message. But, somehow changing the permalink settings from “Default” to “PostName” has resulted in the site being “Access Denied” from certain PC’s, specifically PC in a corporate environment with strict(er) Web Filters.

    So my question – is there a known fix so that changing the permalink settings does not result in sites being blocked in this way? Do you think this is still a host issue? Initial testing suggests the blocking is related to the .htaccess file, which I created as per the instructions in the WP Permalinks Settings page. If I rename the .htaccess I can see the site, but permalinks obviously stop working.

    is there a known fix so that changing the permalink settings does not result in sites being blocked in this way?

    Since this is server specific – not as far as I am aware.

    Do you think this is still a host issue?

    Yes. It sounds like there is an issue with the way the server is handling .htaccess.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Access Denied -> Permalinks .htaccess and Web Filters’ is closed to new replies.