> I never changed the browser configuration when I went from dial-up to
> cable. Then again, since it is a Microsoft product, maybe it's going
> around changing things behind my back and exercising more autonomy
> than it should. I'll check...
> All there is in LAN settings (which I assume will
On Thu, 15 Jan 2004 08:36:38 -0500, Paul Derbyshire
<[EMAIL PROTECTED]> wrote:
Lastly, is this port being exposed to the Internet going to pose
a security risk, or is the fproxy service reasonably robust against
the usual things, e.g. buffer overflow exploits. The only thing I can
That's so
On 15 Jan 2004 at 5:54, S wrote:
> telnet 127.0.0.1
>
> Hit Enter. When the connection opens, type:
>
> HEAD / HTTP/1.0
Had to blind-type this -- nothing echoed.
> HTTP/1.1 302 Moved Temporarily
> Date: Thu, 15 Jan 2004 05:43:59 GMT
> Pragma: no-cache
> Location: /servlet/nodeinfo/
> Expi
On Thu, 15 Jan 2004 06:02:22 -0500
"Paul Derbyshire" <[EMAIL PROTECTED]> wrote:
> at 127.0.0.1: in ie 6.x. I know my ISP (cable) has some sort of
> wonky caching of web pages, as evidenced by intermittent random 500-
> series errors I never got on dial-up and the odd out-of-date page
> comin
Got the windows webinstall executable and ran it less than 2 hours
ago. Node may or may not be running ok, but fproxy is definitely on
the blink. Looked at (without altering) the options, and nothing is
obviously bad, such as say fproxy being turned off.
Symptom:
Server Error
The following err
