Watchguard Firebox X1000, Reference Manual

Page: 87 / 264

Reference Guide 75
http-proxy[205]: [x.x.x.x:8921 x.x.x.x:80] Error while
sending/receiving: Invalid transfer-encoding type
"Identity"
HTTP has a provision for defining the encoding type used in the
page data transfer. The default is called "Identity," which means
that no encoding or transformations are performed on the page
data. The RFC for HTTP 1.1 says the following about identity:
identity: The default (identity) encoding; the use of no
transformation whatsoever. This content-coding is used only in
the Accept-Encoding header, and SHOULD NOT be used in the
Content-Encoding header.
The HTTP Proxy strictly enforces the "should not" provision of the
RFC. It denies the content-encoding type as invalid. Connections
to the offending server should be made through a packet filtered
port 80 service.
init[1]: Pid xx: exit 0 (could also be 1)
This message appears when a process that finished whatever it
was doing is now exiting normally. The xx indicates the Process
ID number.
ipseccfg[] Error, cfg entry (networking.ipsec.
remote_gw.195.sharedkey) must contain a shared key.
Indicates that the ipseccfg was unable to parse a shared key hash
from the configuration file, possibly due to a corrupted
configuration file. Try reconfiguring your VPN tunnel options
and/or Mobile User IPSec options.
ipseccfg[] Ipsec inbound policy (12) maps to a nonexistent
tunnel (xxxxxxxxx)
Indicates that the ipseccfg was unable to determine the correct
routing, possibly due to a corrupted configuration file. Try
reconfiguring your VPN tunnel options and/or Mobile User IPSec
options.
ipseccfg[] No inbound policies configured, aborting ipseccfg
This indicates that your Firebox has the IPSec component, but no
tunnels configured. It is harmless if you are not using IPSec VPN.
If you are using IPSec VPN when this message appears, your
configuration file might be corrupted. Try reconfiguring your
VPN tunnel options and/or your mobile user IPSec tunnel
options.