![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Mon, Jan 10, 2005 at 11:12:05AM -0500, Bob Gorman wrote: > > At 10:48 AM 1/10/2005, David Hummel wrote: > >On Mon, Jan 10, 2005 at 08:13:38AM -0500, Bill Horne wrote: > >> > >> Unless Comcast has started to choke port 80 requests, > > > >That is exactly what is happening. > > I've heard others complain about this, but my port 80 is not blocked > by comcast. If you are experiencing problems with incoming HTTP requests on port 80, I would not rule this out. Change the port to test this. Otherwise, I would guess it's a router or LAN issue at your location. > I personally keep port 80 closed and use https/443 instead. Seems the > simple script attacks that plagued my port 80 don't go there. But you are asking about port 80, no? -David
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |