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 OSX
apache::testtrace
Apache::TestTrace(3) User Contributed Perl Documentation Apache::TestTrace(3)NAME
Apache::TestTrace - Helper output generation functions
SYNOPSIS
use Apache::TestTrace;
debug "foo bar";
info_sub "missed it";
error_mark "something is wrong";
# test sub that exercises all the tracing functions
sub test {
print $Apache::TestTrace::LogFH
"TraceLevel: $Apache::TestTrace::Level
";
$_->($_,[1..3],$_) for qw(emerg alert crit error
warning notice info debug todo);
print $Apache::TestTrace::LogFH "
"
};
# demo the trace subs using default setting
test();
{
# override the default trace level with 'crit'
local $Apache::TestTrace::Level = 'crit';
# now only 'crit' and higher levels will do tracing lower level
test();
}
{
# set the trace level to 'debug'
local $Apache::TestTrace::Level = 'debug';
# now only 'debug' and higher levels will do tracing lower level
test();
}
{
open OUT, ">/tmp/foo" or die $!;
# override the default Log filehandle
local $Apache::TestTrace::LogFH = *OUT;
# now the traces will go into a new filehandle
test();
close OUT;
}
# override tracing level via -trace opt
% t/TEST -trace=debug
# override tracing level via env var
% env APACHE_TEST_TRACE_LEVEL=debug t/TEST
DESCRIPTION
This module exports a number of functions that make it easier generating various diagnostics messages in your programs in a consistent way
and saves some keystrokes as it handles the new lines and sends the messages to STDERR for you.
This module provides the same trace methods as syslog(3)'s log levels. Listed from low level to high level: emerg(), alert(), crit(),
error(), warning(), notice(), info(), debug(). The only different function is warning(), since warn is already taken by Perl.
The module provides another trace function called todo() which is useful for todo items. It has the same level as debug (the highest).
There are two more variants of each of these functions. If the _mark suffix is appended (e.g., error_mark) the trace will start with the
filename and the line number the function was called from. If the _sub suffix is appended (e.g., error_info) the trace will start with the
name of the subroutine the function was called from.
If you have "Term::ANSIColor" installed the diagnostic messages will be colorized, otherwise a special for each function prefix will be
used.
If "Data::Dumper" is installed and you pass a reference to a variable to any of these functions, the variable will be dumped with
"Data::Dumper::Dumper()".
Functions whose level is above the level set in $Apache::TestTrace::Level become NOPs. For example if the level is set to alert, only
alert() and emerg() functions will generate the output. The default setting of this variable is warning. Other valid values are: emerg,
alert, crit, error, warning, notice, info, debug.
Another way to affect the trace level is to set $ENV{APACHE_TEST_TRACE_LEVEL}, which takes effect if $Apache::TestTrace::Level is not set.
So an explicit setting of $Apache::TestTrace::Level always takes precedence.
By default all the output generated by these functions goes to STDERR. You can override the default filehandler by overriding
$Apache::TestTrace::LogFH with a new filehandler.
When you override this package's global variables, think about localizing your local settings, so it won't affect other modules using this
module in the same run.
TODO
o provide an option to disable the coloring altogether via some flag
or import()
AUTHOR
Stas Bekman with contributions from Doug MacEachern
perl v5.16.2 2011-02-07 Apache::TestTrace(3)