Skip to comments.Anybody having this problem
Posted on 03/18/2012 5:11:26 AM PDT by usnavy_cop_retired
I tried to link to a newsletter from Dick Morris and got this notice every time I tried; 403 Forbidden nginx/0.7.65, anybody else having this problem. My internet in the Philippines is slow, but I have never received this code. This is the site I was trying to access; http://www.dickmorris.com/blog/
Nope. It works ok for me.
Works here too. Make sure there are no characters after the final / in the address.
I have super fast connections and it is taking forever to download, nearly two minutes and all I have is the date of the debate.
Just timed out.
Could it be your ISP address has been blacklisted by this site?
Sounds like the server was too busy sucking on toes to respond.
Worked ok here
Being unable to read Dick Morris is not a problem, it’s a feature!
Works here. Try clearing your cache and restarting your browser.
I tried that, but still get the same message. I know that some websites block the Philippines, (and other countries). This is a common problem with some DOD sites.
For a long time I was unable to access the Tricare Manuals because DOD blocked all Phillipine ISP’s, but after I complained to the head honcho, it finally was unblocked.
That was a real battle since they tell us we are responsible to know the rules and regulations contained in the Manuals, but they were blocking access to the Manuals.
They just had a hard time understanding that if they refused us access to the rules and regulations then they were leaving their selves open for a class action law suit if they denied our claims for reimbursements based on rules/regulations that we had no access to. LOL
I think its pretty obvious that Dick Morris is forbidden. Can’t say I disapprove of that ruling.
Coolness! I just downloaded/installed TOR. Checked a known blocked site and it went right to it. Thanks.
I have been assisting with an evaluation of the TOR system to see how it would perform as a backup for FreeRepublic.
It involves adding P2P to the basic TOR system. The browser would remain the same but there would be a button to join a P2P version of FR.
In a nutshell, FR users would install a modified version of the TOR browser bundle. All FR users would be going through a TOR proxy chain and the last server in the chain would link to a FR users ip instead of a normal server on the web.
Security would be very high with encryption at every point. Usually the last server in a TOR chain gets a look at your traffic unencrypted since the server on the web needs plain text to function. The modified TOR system when used for FR P2P could have an encrypted link from the user at one end right through to the user on the other. The only exposed data would be the final destination ip address. I am pondering ways to make that more difficult to discern.
Speed of such a system would be slow compared to what users expect from FreeRepublic. But speed is not everything, this system would store data on each users machine and when you requested a page it would be served by another FR user from his/her machine...this data would be encrypted for extra security. You could once again post full text of articles from any source as there would be no way to discover who placed the item or where it was being stored.
This system would be hard to monitor compared to what we have now. It could not be censored or easily shut down. The entire TOR network would have to be shut off to disable it. Rogue users could be disciplined by those with the correct admin pass phrases. The reason for using TOR to facilitate P2P is added security and the fact that to take it down TOR itself would have to be destroyed...and that would raise a huge stink!
To the TOR system the P2P users machines would be identical to any random server located on the network....TOR itself would not be modified or compromised in any way.
Adding secure file transfer abilities to the P2P client would soon ensure a huge user base of non-Freepers would be storing FR data and enlarging the pool of possible surveillance targets to an unmanageable level. It would also be a nice way to transfer music and other media files without the inherent risk of an exposed ip that using current methods have.