Httpd proxy on AIX: failed to connect SSL Post: 303042275

Sponsored Content

Special Forums IP Networking Proxy Server Httpd proxy on AIX: failed to connect SSL Post 303042275 by Neo on Friday 20th of December 2019 04:10:01 AM

12-20-2019

Administrator

Code:

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

Reference:

Controls the verbosity of the ErrorLog - Apache HTTP Server Version 2.4

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to connect to FTP server which requires SSL authentication?

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...

2. AIX

AIX Remote Connect Fail With �No more multiple IP addresses to connect� Error

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.

3. Web Development

Apache proxy for web app with ssl

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...

4. Web Development

Http connect to proxy to websockets

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...

5. Web Development

Httpd proxy with mod_jk,ssl only on login page using .htacess

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...

6. Programming

Failed SSL Connection Attempt

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:...

7. Red Hat

Proxy tunneling failed: ForbiddenUnable to establish SSL connection.

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)...

LEARN ABOUT OPENSOLARIS

ssh-http-proxy-connect

ssh-http-proxy-connect(1)					   User Commands					 ssh-http-proxy-connect(1)

NAME

       ssh-http-proxy-connect - Secure Shell proxy for HTTP

SYNOPSIS

       /usr/lib/ssh/ssh-http-proxy-connect [-h http_proxy_host]
	    [-p http_proxy_port] connect_host connect_port

DESCRIPTION

       A  proxy command for ssh(1) that uses HTTP CONNECT. Typical use is where connections external to a network are only allowed via a proxy web
       server.

OPTIONS

       The following options are supported:

       -h http_proxy_host    Specifies the proxy web server through which to connect. Overrides the HTTPPROXY and http_proxy environment variables
			     if they are set.

       -p http_proxy_port    Specifies the port on which the proxy web server runs. If not specified, port 80 is assumed. Overrides the HTTPPROXY-
			     PORT and http_proxy environment variables if they are set.

OPERANDS

       The following operands are supported:

       http_proxy_host	  The host name or IP address (IPv4 or IPv6) of the proxy.

       http_proxy_port	  The numeric port number to connect to on http_proxy_host.

       connect_host	  The name of the remote host to which the proxy web server is to connect you.

       connect_port	  The numeric port number of the proxy web server to connect you to on http_proxy_host.

EXAMPLES

       The recommended way to use a proxy connection command is to configure the ProxyCommand in ssh_config(4) (see  Example  1  and  Example  2).
       Example 3 shows how the proxy command can be specified on the command line when running ssh(1).

       Example 1 Setting the proxy from the environment

       The following example uses ssh-http-proxy-connect in ssh_config(4) when the proxy is set from the environment:

	 Host playtime.foo.com
	     ProxyCommand /usr/lib/ssh/ssh-http-proxy-connect 
		 playtime.foo.com 22

       Example 2 Overriding proxy environment variables

       The following example uses ssh-http-proxy-connect in ssh_config(4) to override (or if not set) proxy environment variables:

	 Host playtime.foo.com
	     ProxyCommand /usr/lib/ssh/ssh-http-proxy-connect -h webcache 
		 -p 8080 playtime.foo.com 22

       Example 3 Using the command line

       The following example uses ssh-http-proxy-connect from the ssh(1) command line:

	 example$ ssh -o'ProxyCommand="/usr/lib/ssh/ssh-http-proxy-connect 
	     -h webcache -p 8080 playtime.foo.com 22"' playtime.foo.com

ENVIRONMENT VARIABLES

       HTTPPROXY	Takes the http_proxy_host operand to specify the default proxy host. Overrides http_proxy if both are set.

       HTTPPROXYPORT	Takes the http_proxy_port operand to specify the default proxy port. Ignored if HTTPPROXY is not set.

       http_proxy	URL format for specifying proxy host and port.

EXIT STATUS

       The following exit values are returned:

       0     Successful completion.

       1     An error occurred.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWsshu			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Stable			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       ssh(1), ssh-socks5-proxy-connect(1), ssh_config(4), attributes(5)

SunOS 5.11							    24 Oct 2001 					 ssh-http-proxy-connect(1)