No announcement yet.

ISP Blocks HTTP Requests

  • Filter
  • Time
  • Show
Clear All
new posts

  • ISP Blocks HTTP Requests

    My ISP blocks all http requests. What's funny is they allow FTP but not HTTP. I don't understand how it's ok to run an ftp but I can't host simple xperiments of my work.

    Anyway... The only somewhat fix I came up with was on my webserver, create an FTP login script that will connect me to my computer. It worked, but then to display and run the files, there were problems and it's a lot of work.

    Someone advised me that https:// may work. He really didn't gie me much of an explanation.

    So I ask you, is there a workaround?

    I'm not trying to do anything devious, it's just that my web server does not support Coldfusion, Flash Comm Server, etc. So there is basically no way of showing my work online, since I really don't want to pay for another server, simply for experiments.


  • #2
    If you ISP is actively blocking the traffic then it is not advisable to try to get around this. You can and likely will lose your account with them; or may just be billed for a commercial account. If this does not concern you then you should probably spend the effort finding a better ISP that does not block your traffic.

    Are they blocking http requests? or simply traffic with a destination of port 80?
    if it gets me nowhere, I'll go there proud; and I'm gonna go there free.


    • #3
      Originally posted by converge
      If you ISP is actively blocking the traffic then it is not advisable to try to get around this.
      That would depend on why they are blocking traffic. For instance, the TOS for my service level specify that I cannot run serversm and the ISP actively blocks incoming connections on port 80. However, multiple discussions with them reveal that the block was/is in place to stop Code Red. They don't care if I run a personal webserver; the company defines a "server" as a commercial server.

      That being said, https will work because it (typically) runs on a different port. If you configured your web server to use a different port (8080 is common), then you can bypass the ISP-level block.


      • #4
        Well I tryed using differernt ports such as 8080, and a few others that won't come to mind right know.

        I spoke to someone on the phone from cablevision, and they said "We block all HTTP requests".

        Why don't I leave? Simple, no way in the world will I get nearly as fast download and upload speeds anywhere.

        Now you say https will work?


        • #5
          HTTPS works over either SSL or TLS. If your ISP is blocking HTTP requests at the application level, but not SSL/TLS, then it will work.

          If they are blocking by port but include 8080, however, then it would seem your ISP is going to get upset by your activities (if they ever find out). Just something to consider.


          • #6
            Ok I appreciate the advise.

            I was running Apache, IIS seems to give me nothing but headaches.

            Do you have any links to tutorials on setting up https:// on apache?