There was enough time so I decided to bloghop. Then after minutes of bloghopping, I chanced upon a site that has a link to the blog site of a RESPECTABLE blogger. It has been a while since I last visited the site but I usually do not leave a comment. The post was interesting enough to elicit a ‘safe’ comment from me. I had to go back because I am interested to know the reply.HTTP: Forbidden - that was what I saw at the upper portion of the page when I tried to access the site. I am not tech savvy so the first thing that crossed my mind was there must be something wrong with the server again. I went to another site which I recalled to have included the RESPECTABLE blogger’s site. The same note - HTTP: Forbidden was on the page.
Was it deliberate or not to forbid me from gaining access to the site? Boy, was I so naïve.
Maybe it was not deliberate. Maybe the page was not available that time.
Maybe it was deliberate. There must be a reason. Maybe I was banned for life, who knows? *grins*
Am I offended? No, of course not. If I am, I should have mentioned the name of the site, or pounced on the person. Everybody has his/her preferences and reasons so no problem. Kanya-kanya lang yan, a friend told me once when I posted some observations.--------
Addendum:
I visited one of those sites. After reading a post of a genius blogger, I felt so exhausted. Never did I realize that unconstructive posts could drain one’s energy. There is no doubt that the blogger has extremely good writing style but the obnoxiousness crossed out the ingenuity. “What do you care, you nincompoop?” this is what the blogger might toss at me upon knowing that his extraordinary blog site is mugged up critically by a newbie. Or maybe worse. That is if I'll mention the blogsite.*smirk*
A 403 error forbids the browser from reading certain content within the server - it's not really forbidding *you*, per se. It usually occurs when a link is broken and certain permissions weren't granted by the server, like viewing the contents of a driectory. It's a technical problem on the blog owner's end, maybe a result of a change of admin settings or broken links, and I don't think it's malicious: I mean, that'd be childish in the extreme in his her part ;) If he/she were to ban you or your IP, you'd have seen a 401 error instead. Hope that helps clear things up.. for reference: http://www.checkupdown.com/status/E403.html
ReplyDeleteOne of the reasons if I may add is the anti-spam software implemented by the blog owner. Likewise, if the internal setting is set to block insecure proxies which the anti-spam software identified, then that's it.
ReplyDeleteHere, there are so many http: Forbidden all because of the software filtering (used by the the telco) different sites and IPs. One word like "sex" would do it. I don't know how many words are there in their database.
you piqued my curiosity. hmmm, who could that genius blogger might be?
ReplyDeleteha ha am not telling, slim! i do not want to invite a mob. i used to admire the blogger's creations, not until the other day. i did feel exhausted, literally, didnt get amused nor entertained.
ReplyDeletehindi pala ako nag-iisa! thanks single and niceheart for dropping by.
ReplyDeleteAnd who, in his/her right mind, would ban a nice blogger like you? :-) Puera flattery, Bing.
ReplyDeleteI've never encountered an HTTP error on a blog before, mostly I get the 404 error page. The link was broken as most cases in my experience.
ReplyDeletebuti ka pa, jhay! ako ang dalas.
ReplyDelete