Description: Controls the verbosity of the ErrorLog
Syntax: LogLevel [module:]level [module:level] ...
Default: LogLevel warn
Context: server config, virtual host, directory
Status: Core
Module: core
Compatibility: Per-module and per-directory configuration is available in Apache HTTP Server 2.3.6 and later
LogLevel adjusts the verbosity of the messages recorded in the error logs (see ErrorLog directive).
The following levels are available, in order of decreasing significance:
Level Description Example
emerg Emergencies - system is unusable. "Child cannot open lock file. Exiting"
alert Action must be taken immediately. "getpwuid: couldn't determine user name from uid"
crit Critical Conditions. "socket: Failed to get a socket, exiting child"
error Error conditions. "Premature end of script headers"
warn Warning conditions. "child process 1234 did not exit, sending another SIGHUP"
notice Normal but significant condition. "httpd: caught SIGBUS, attempting to dump core in ..."
info Informational. "Server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers)..."
debug Debug-level messages "Opening config file ..."
trace1 Trace messages "proxy: FTP: control connection complete"
trace2 Trace messages "proxy: CONNECT: sending the CONNECT request to the remote proxy"
trace3 Trace messages "openssl: Handshake: start"
trace4 Trace messages "read from buffered SSL brigade, mode 0, 17 bytes"
trace5 Trace messages "map lookup FAILED: map=rewritemap key=keyname"
trace6 Trace messages "cache lookup FAILED, forcing new map lookup"
trace7 Trace messages, dumping large amounts of data "| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"
trace8 Trace messages, dumping large amounts of data "| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"
When a particular level is specified, messages from all other levels of higher significance will be reported as well.
E.g., when LogLevel info is specified, then messages with log levels of notice and warn will also be posted.
Using a level of at least crit is recommended.
For example:
LogLevel notice
Note
When logging to a regular file, messages of the level notice cannot be suppressed and thus are always logged. However, this doesn't apply when logging is done using syslog.
Specifying a level without a module name will reset the level for all modules to that level.
Specifying a level with a module name will set the level for that module only.
It is possible to use the module source file name, the module identifier, or the module identifier with the trailing _module omitted as module specification.
This means the following three specifications are equivalent:
LogLevel info ssl:warn
LogLevel info mod_ssl.c:warn
LogLevel info ssl_module:warn
It is also possible to change the level per directory:
LogLevel info
<Directory "/usr/local/apache/htdocs/app">
LogLevel debug
</Directory>
Per directory loglevel configuration only affects messages that are logged after the request has been parsed and that are associated
Hello,
I tried searching through lot of threads for a solution but couldn't fetch the exact solution, so I am creating a new thread.
I am trying to connect to a FTP server
1) using a simple FTP command, it gives the error :
534 Policy requires SSL.
Login failed.
2) using SFTP... (19 Replies)
We have a production server at a client site running AIX. And recently when users are trying to connect to it via telnet, it prompts "No more multiple IP addresses to connect".
Can I know what does this error mean? and how to rectify this?
Thanks. (2 Replies)
I have a ubuntu server running subsonic as a web app. Currently the web interface is available from port 4040 for https connections and 4141 for https connections with the context /subsonic as follows:
http://mydomain:4040/subsonic
https://mydomain:4141/subsonic
I would like to loose the port... (0 Replies)
I am having a hard time with this one. We have a websocket server listening on port 80 at myserver.com/wsDemo?ID=12. We need to test a client program by connecting it to this server through a proxy. I am trying nginx 1.2.7 as the proxy on port 8080, running on proxy-server. We want the client to... (1 Reply)
Hi all, I have a web app with the following pages, browse.jsp and shopping.jsp. I want to protect shopping.jsp with https. (https is only between browser and apache httpd server.)The https for the shopping.jsp page will terminate at the web server.
From web server to tomcat application server... (0 Replies)
The below error message I started seeing using Ubuntu 14.04 and was wondering if the forum has seen it because I cant seem much on the net for this:
perl -e 'use IO::Socket::SSL qw(debug3);IO::Socket::SSL->new(PeerAddr=>"10.0.0.100",PeerPort=> 443,Proto=>"TCP") or die $!'
DEBUG:... (1 Reply)
Tryied both ways curl and wget
wget --no-check-certificate https://mysitet.it:61617
--2017-05-05 17:29:02-- https://mysitet.it:61617/
Connecting to myproxy:8080... connected.
Proxy tunneling failed: ForbiddenUnable to establish SSL connection.
curl https://mysite.it:61617
curl: (56)... (3 Replies)
Discussion started by: charli1
3 Replies
LEARN ABOUT DEBIAN
net::proxy::connector::connect_ssl
Net::Proxy::Connector::connect_ssl(3pm) User Contributed Perl Documentation Net::Proxy::Connector::connect_ssl(3pm)NAME
Net::Proxy::Connector::connect_ssl - Create SSL/CONNECT tunnels through HTTP proxies
SYNOPSIS
# sample proxy using Net::Proxy::Connector::tcp
# and Net::Proxy::Connector::connect_ssl
use Net::Proxy;
# listen on localhost:6789
# and proxy to remotehost:9876 through proxy.company.com:8080
# using the given credentials
my $proxy = Net::Proxy->new(
in => { type => 'tcp', port => '6789' },
out => {
type => 'connect_ssl',
host => 'remotehost',
port => '9876',
proxy_host => 'proxy.company.com',
proxy_port => '8080',
proxy_user => 'jrandom',
proxy_pass => 's3kr3t',
proxy_agent => 'Mozilla/4.04 (X11; I; SunOS 5.4 sun4m)',
},
);
$proxy->register();
Net::Proxy->mainloop();
DESCRIPTION
"Net::Proxy::Connecter::connect_ssl" is a "Net::Proxy::Connector" that uses the HTTP CONNECT method to ask the proxy to create a tunnel to
an outside server. The data is then encrypted using SSL.
Obviously, you'll need a server that understands SSL (or a proxy using "Net::Proxy::Connector::ssl") at the other end.
This connector is only an "out" connector.
In addition to the options listed below, this connector accepts all "SSL_..." options to "IO::Socket::SSL". They are transparently passed
through to the appropriate "IO::Socket::SSL" methods when upgrading the socket to SSL.
CONNECTOR OPTIONS
"Net::Proxy::Connector::connect" accepts the following options:
"out"
o host
The destination host.
o port
The destination port.
o proxy_host
The web proxy name or address.
o proxy_port
The web proxy port.
o proxy_user
The authentication username for the proxy.
o proxy_pass
The authentication password for the proxy.
o proxy_agent
The user-agent string to use when connecting to the proxy.
AUTHOR
Philippe 'BooK' Bruhat, "<book@cpan.org>".
HISTORY
Because "Net::Proxy" blocks when it tries to connect to itself, it wasn't possible to pass an SSL-encrypted connection through a proxy with
a single script: you needed one for the SSL encapsulation, and another one for bypassing the proxy with the "CONNECT" HTTP method.
See "Net::Proxy::Connector::connect" and "Net::Proxy::Connector::ssl" for details.
COPYRIGHT
Copyright 2007 Philippe 'BooK' Bruhat, All Rights Reserved.
LICENSE
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.10.1 2009-10-18 Net::Proxy::Connector::connect_ssl(3pm)