Watchguard Firebox X1000, Reference Manual

Page: 86 / 264

CHAPTER 5: Common Log Messages
74 WatchGuard Firebox System
this file indicates that firewalld is taking a long time to create it. A
possible cause is that the configuration file is corrupted.
http-proxy[]: no proxy services configured -- exiting
Indicates that no services defined on the Firebox make use of the
HTTP Proxy. The HTTP Proxy process starts, determines there are
no rules for the process, and then exits.
http-proxy[] proxy connect timeout
Indicates that the HTTP proxy sent a SYN to either an internal or
external HTTP server, but did not receive a SYN-ACK response
within the period of time specified in the Firebox configuration
file. The cause may be a downed HTTP server. The Proxy Connect
Timeout defines the amount of time (in seconds) that proxies wait
before they stop trying to forward a connection to an unreachable
or non-responsive host. After a connection is established, the
standard proxy timeout values apply. You may try raising this
value by adding (or editing) the following property in the
configuration file:
default.proxies.http.timeout: 600
http-proxy[] [x.x.x.x:1620 x.x.x.x:80] server was
unexpectedly closed
Indicates that the server closed the connection before the data
transfer was complete. This can be caused by busy Web servers or
bad network connectivity.
http-proxy[668] [x.x.x.xx:4584 x.x.x.x:80\] Response
denied: Content type required
One feature of the HTTP Proxy is MIME type content checking.
Web servers should send this information, but some do not. The
message above tells you that the HTTP Proxy denied the page
because it lacks a content type.
Some custom applications transfer data using pseudo-HTTP
transfers to enable them to work through most types of HTTP
proxies. If this message appears when a Web page is not being
accessed, it may be because data transfers are being attempted
using HTTP on ports other than 80. The Proxied-HTTP service (as
distinct from the HTTP proxy) proxies any outgoing port, not just
80.