Damn You, Websense!

[Chimera]

Or more accurately, the people in my network area.

I have been pretty much parking on Domebo during the day, posting between calls or while waiting on hold.

Now suddenly it's blocked, as a social networking site.

Straight Dope isn't. Which tells me that some jackass in the back room was monitoring things, saw me hooked up to the website and decided to block it.

Bastard.

[Oliveloaf]

Kinda creepy. Sorry to hear that.

I am always browsing stuff while I am on hold, or having some necessary but low-brain-effort call.

[McNutty]

Well, if they don't block by IP, you can use http://importantworkbusiness.ignorelist.com with the caveat that the cookies don't work correctly so you have to log in anew each time you visit. We can just keep adding new aliases as they catch on to the old ones.

[Chimera]

Thanks, I'll try that tomorrow.

[ivan astikov]

Thanks, I'll try that tomorrow.

Excuse me, should you be in here?

[Chimera]

Hey, I'm no longer stoned. Er....stone.

[ivan astikov]

Hey, I'm no longer stoned. Er....stone.

Early release, eh? I'm proud of you.

[Jaglavak]

Well, if they don't block by IP, you can use http://importantworkbusiness.ignorelist.com.....

:: golf clap ::

[troubleagain]

It was blocked for me for a while, as a "potentially harmful site with little or no benefit." But when they moved hosts, it got "unblocked" for me. Giraffeboard is still blocked, I think.

[What Exit?]

Well, if they don't block by IP, you can use http://importantworkbusiness.ignorelist.com with the caveat that the cookies don't work correctly so you have to log in anew each time you visit. We can just keep adding new aliases as they catch on to the old ones.

What would it take to propagate a DNS record for 67.207.138.196 = domebo.net
I use the IP address of the Dope at work. It causes a few very minor problems, but not much but at this point the domebo IP address does not resolve.

As an example this link should resolve to this thread. http://67.207.138.196/forum/viewtopic.php?f=10&t=1359 But it does not.

[McNutty]

What would it take to propagate a DNS record for 67.207.138.196 = domebo.net
I use the IP address of the Dope at work. It causes a few very minor problems, but not much but at this point the domebo IP address does not resolve.

As an example this link should resolve to this thread. http://67.207.138.196/forum/viewtopic.php?f=10&t=1359 But it does not.

It's not a DNS issue, it's a virtual hosting issue. When you ask for a site by name, you're effectively saying "hey, 67.207.138.196, please give me domebo.net", so it gives you that site. If you just use the IP address, you're saying "hey 67.207.138.196, please give me your default web site", which in this case is my personal site which has a blank front page and no "/forum". So the server needs to be reconfigured to make domebo.net the default site. I don't mind doing this, but it will require a restart of the web server, so I'll do it later when there's not so much board traffic.

[What Exit?]

What would it take to propagate a DNS record for 67.207.138.196 = domebo.net
I use the IP address of the Dope at work. It causes a few very minor problems, but not much but at this point the domebo IP address does not resolve.

As an example this link should resolve to this thread. http://67.207.138.196/forum/viewtopic.php?f=10&t=1359 But it does not.

It's not a DNS issue, it's a virtual hosting issue. When you ask for a site by name, you're effectively saying "hey, 67.207.138.196, please give me domebo.net", so it gives you that site. If you just use the IP address, you're saying "hey 67.207.138.196, please give me your default web site", which in this case is my personal site which has a blank front page and no "/forum". So the server needs to be reconfigured to make domebo.net the default site. I don't mind doing this, but it will require a restart of the web server, so I'll do it later when there's not so much board traffic.

That would be great. Very cool of you.

[McNutty]

Actually, it turned out to be even easier than that. The "default site" was actually set to test.domebo.net, which we never ended up using during the transition, so all I had to do was make test.domebo.net a symlink to domebo.net. No restart required. Should work now (with the caveat about cookies).

[Chimera]

Hah! And that seems to have made it bypass websense now!

But for how long!

How Long!

[What Exit?]

Actually, it turned out to be even easier than that. The "default site" was actually set to test.domebo.net, which we never ended up using during the transition, so all I had to do was make test.domebo.net a symlink to domebo.net. No restart required. Should work now (with the caveat about cookies).

I just tried it and it worked great. I did have to log in of course.

[McNutty]

Another thing I could probably do is enable SSL. That will get around a lot of web filters. It would have to be using a self-signed certificate, though, so you'd have to add the certificate to your local exceptions in order to get your browser to use it, but once you're using SSL, they won't know what the traffic is other than by recognizing it's to that same IP.

[Chimera]

Then of course, a half hour later it was blocked again. Drat.

Went to importantworkbusiness.ignorelist.com. Got the main page. Click on forums. Blocked, because it's pointing back at the domebo forums page.