squid, wordpress and blogs...

[murraybiscuit]

so i've developed a site for a client in wordpress.
i put it up on a demo url but some of the css and js doesn't work when browsing behind their lan.
squid is blocking wordpress sites aka "blogs/personal pages".
which seems a bit ridiculous, but i'm not sure there's a lot i can do about it because head office in germany controls the proxy.

anyways, before i start wrangling with sysadmins, i want to know if it's common practice to block wordpress sites and whether this is a default squid rule or whether they implemented it specifically.

if wordpress is a general proxy no-no, are other cms options also commonly disallowed? i'm just trying to understand common practice here before i start making suggestions.

 

[Anthro]

most rules in squid / firebox / ipcop work on a meta tag in the site itself, the categories set up in the firewall is normally defined as 'personals and dating' ie facebook etc etc
So the rule itself is 'encompassing' and looks at 'tag lines' inside the website

 

[murraybiscuit]

yeah, it looks like the rules are a bit cleverer than that
they're blocking the /wp-content/ dir in the worpress install, but allowing requests to wp-includes/ through.
if it's just this client who does this, i'm happy to ask them to relax the rules for this site, but if it's general practice for large companies to filter wordpress sites, i'm going to need to come up with another solution.
i can understand filtering fb, youtube, twitter and the like, but isn't filtering ALL wordpress sites excessive?

 

[Anthro]

Thing is, my company runs their website on wordpress - easy and intuitive enough to use for the purpose, so i guess it depends on the content description etc ..