I have been told that access to example.com has been deliberately
blocked, this is not a misconfiguration. I am not at liberty to say why.
You may start to find others having problems accessing it.
UGH! This is a legitimate testing site, one we can always count on being
up and returning a
On 6/1/15 12:11 PM, Karen Etheridge wrote:
I have been told that access to example.com http://example.com has
been deliberately blocked, this is not a misconfiguration. I am not
at liberty to say why. You may start to find others having problems
accessing it.
UGH! This is a legitimate
I have been told that access to example.com has been deliberately
blocked, this is not a misconfiguration. I am not at liberty to say
why. You may start to find others having problems accessing it.
-Nigel
I Karen,
I have tracked it down. Websense here is blocking access to
example.com,
I Karen,
I have tracked it down. Websense here is blocking access to
example.com, which clearly it shouldn't do because that's a legitimate
site. I will talk to the people who maintain it.
In the meantime, it's a nice edge case to find.
-Nigel
Hi Nigel,
What is up with these test
I had always understood example.com to be reserved for documentation and
that it should not be relied upon to exist.
http://tools.ietf.org/html/rfc6761
On Mon, Jun 1, 2015 at 12:11 PM, Karen Etheridge p...@froods.org wrote:
I have been told that access to example.com has been deliberately
Now you have me wondering/searching where I read that example.com was a
good place for pointing tests at, that would serve a reliable response...
and what other location, if not this, should be used instead... (I want to
test basic things like a real 200 OK or 302 Found from an http GET or POST.)
