On Thursday 13 April 2017 19:26:52 Daniel wrote:
> Always match slashes!
>
> ProxyPass / "fcgi://127.0.0.1:9000/"
>
That leads to:
File not found.
with httpd error log info:
[Thu Apr 13 23:01:34.559768 2017] [proxy_fcgi:debug] [pid 4066:tid
140533607941888] mod_proxy_fcgi.c(913): [cl
On Thursday 13 April 2017 15:27:01 Frank wrote:
> On 13/04/17 02:18 PM, John Iliffe wrote:
> > I'm still trying to figure out what is actually happening here and I
> > have a result that is truly confusing now.
> >
> > I decided to just route everything to php-fpm, mainly to check that it
> > is a
Always match slashes!
ProxyPass / "fcgi://127.0.0.1:9000/"
2017-04-13 21:27 GMT+02:00 Frank :
>
>
> On 13/04/17 02:18 PM, John Iliffe wrote:
>
>> I'm still trying to figure out what is actually happening here and I
>> have a result that is truly confusing now.
>>
>> I decided to just route every
On 13/04/17 02:18 PM, John Iliffe wrote:
I'm still trying to figure out what is actually happening here and I
have a result that is truly confusing now.
I decided to just route everything to php-fpm, mainly to check that it
is actually active, and I used a file that would have been routed ther
Hi Peter,
your setup should be correct, the self-signed certificate is shown in ssllabs
result because they test a connection with a client that does not support SNI.
Here you can find more info:
https://community.qualys.com/thread/16759-dead-link-in-devssllabscom-if-second-certificate-is-not-tr
I'm still trying to figure out what is actually happening here and I have a
result that is truly confusing now.
I decided to just route everything to php-fpm, mainly to check that it is
actually active, and I used a file that would have been routed there by
ProxyPass/ProxyPassMatch anyhow, so I
Hello,
I tried to investigate this issue on my installations (I have it too),
but didn't come to any conclusion. Here (scroll all the way down)
someone suggest that moving it to /dev/shm fixes the problem:
https://serverfault.com/questions/400089/apache2-sslsessioncache-running-but-not-working
Dear experts,
Unfortunately, I have not been able to make progress on this issue. Do
you have any suggestions how to investigate?
Thanks a lot,
Peter
On 03/23/2017 02:09 PM, Peter Thomassen wrote:
> Hi,
>
> Using Apache 2.4.10 on Ubuntu, I configured a bunch of virtual hosts
> with SSL, plus an
Hi Luca,
I increased the LogLevel to debug, but nothing related to the issue came up.
However, looking in /proc/$PID/fd/, where $PID is the process ID of an
Apache process, I find that there are two symbolic links pointing to
/run/lock/apache2/ssl-cache.19037 # number changes after restart
Found out what the problem is.
Printer web site (and the II server to) has gateway address of vyos
(router/firewall) which is Nating the LAN.
The traffic for my.server.IP is being NATed and of course replies get lost. I
was not capturing the traffic in the correct machine.
Thanks for your t
On Wednesday 12 April 2017 22:24:03 Frank wrote:
> On 12/04/17 08:36 PM, John Iliffe wrote:
> > See below.
> >
> > On Wednesday 12 April 2017 20:02:10 Frank wrote:
> >> On 12/04/17 05:34 PM, John Iliffe wrote:
> >>> I am converting my web pages from mod_php to php-fpm, following the
> >>> directio
What happens if you try to access http://10.0.0.130/ from your dektop computer
inside the LAN
Type it exactly like that with a / (slash) at the end. If you can access it ,
check if your proxy has access to your printer’s IP maybe a firewall or
something is in the way.
From: da...@di.ubi.
Hi All,
Can someone please confirm if Openssl 1.0.2.1000 is compatible with Apache
2.4.10.
I'm trying to disable the TLSv1.0 in the httpd-ssl.conf file, but getting the
below error while restarting the apache.
SSLProtocol: Illegal protocol 'TLSv1.1'
Regards,
Krishna
This message and any att
Hello all.
I want to use apache as a reverse proxy for an internel IIS site. I was unable
to Setup Reverse proxy, so, for testing purposes, my internal site is a network
printer web page.
My Setup:
Internet -> Internet Ip address --→ printer web server
(dns we
Thanks for your answer Luca !
The problem is that, I need this to work under Apache 2.2(also), and
"if" seems to be available only on 2.4+.
I have done some dirty work around, which seems to do the job:
==
http://1.1.1.1/";>
ProxySet connectiontimeout=60 timeout=30
Rewrite
Hi!
2017-04-12 20:42 GMT+02:00 Gryzli Bugbear :
> Hi to all,
>
> I want to make conditional forward proxy within Apache ,based on request
> header if a given request header exists, I want to proxy the request, if
> not, not proxy
> and also I need to do this NOT with RewriteRule and [P] flags.
>
16 matches
Mail list logo
