This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain information that is confidential and
protected by law from unauthorized disclosure. Any unauthorized review, use,
disclosure or distribution is pro
Just to close this out, m#regex# worked perfectly, thanks for the tip.
On Thu, Aug 25, 2016 at 4:27 PM, Eric Covener wrote:
> On Thu, Aug 25, 2016 at 3:59 PM, Brian A. Davis
> wrote:
> >
>
> The limitation is that you cannot use the separator inside the regex,
> even when you escape it. It's
We have an Apache proxy front ended by an F5 load balancer. In it we serve
mixed content, including Weblogic content from an application server and
straight flex content from another webserver. The proxy is running HTTP and
the HTTPS from the load balancer is terminated at the proxy level. Th
I will investigate that.
On Thu, Aug 25, 2016 at 4:48 PM, Daniel wrote:
> Why not just use the directive "UseCanonicalName on"?
>
> El 25/8/2016 10:27 p. m., "Eric Covener" escribió:
>
>> On Thu, Aug 25, 2016 at 3:59 PM, Brian A. Davis
>> wrote:
>> >
>>
>> The limitation is that you cannot u
I'm not sure if that will working when using Apache for a forward proxy.
I only want to allow proxied request to *.foo.com. where foo.com is the
domain of the target of the request, not the domain of the apache server.
On Thu, Aug 25, 2016 at 4:48 PM, Daniel wrote:
> Why not just use the direc
Why not just use the directive "UseCanonicalName on"?
El 25/8/2016 10:27 p. m., "Eric Covener" escribió:
> On Thu, Aug 25, 2016 at 3:59 PM, Brian A. Davis
> wrote:
> >
>
> The limitation is that you cannot use the separator inside the regex,
> even when you escape it. It's a limitation in th
On Thu, Aug 25, 2016 at 3:59 PM, Brian A. Davis wrote:
>
The limitation is that you cannot use the separator inside the regex,
even when you escape it. It's a limitation in the expression engine
used for If, not the regex library.
You can use m#...# in your case.
--
Eric Covener
cove...@gmai
Hello,
I'm trying to reject requests hitting my apache proxy which are NOT going
to *.foo.com, *.foo.com:443 or *.foo.com/blahblahblah. I'm trying to avoid
bogus requests like foo.com.baddomain.com.
The regex I'm using is:
\.foo.com(?:\:\d{2,5}|\/.*)?$
This is working exactly how I want on http
Ok, the standard ubuntu 14.04 openssl is too old. it does not support openssl.
that is why the ppa also unstalls a newer one.
> Am 25.08.2016 um 18:21 schrieb Max Meyer :
>
> The webserver is Ubuntu 14.04
>
> I used the ppa from Ondřej Surý for the apache installation.
>
> https://launchpad.ne
The webserver is Ubuntu 14.04
I used the ppa from Ondřej Surý for the apache installation.
https://launchpad.net/~ondrej/+archive/ubuntu/apache2
The client is Linux Mint 17.3 (which is basically Ubuntu 14.04).
For h2load I built nghttp2 from source:
git clone https://github.com/tatsuhiro-t/ng
Ok, both clients do not provide the server name via the TLS SNI extension. That
is strange. How did you get the server/h2load installed on your Ubuntu? Default
Ubuntu comes without mod_http2 AFAIK...(and which Ubuntu is it?) Thanks!
> Am 25.08.2016 um 16:49 schrieb Max Meyer :
>
> I created a n
I created a new certificate, now the cert name matches but h2load still
falls back to HTTP/1.1
Here is the error.log after apache restart
---
[Thu Aug 25 16:38:12.351311 2016] [ssl:info] [pid 3931] AH01887: Init:
Initializing (virtual) servers for SSL
[Thu Aug 25 16:38:12.351381 2016]
The following line does not look good:
[Thu Aug 25 15:19:43.851331 2016] [ssl:warn] [pid 4275] AH01909:
localhost:443:0 server certificate does NOT include an ID which matches the
server name
Can you make sure that all names do align? Maybe tweak /etc/hosts to make it
match your localhost?
>
Hi Stefan,
thanks for your answer.
I did what you suggested. Here is the error.log
---
[Thu Aug 25 15:19:43.850756 2016] [ssl:info] [pid 4275] AH01887: Init:
Initializing (virtual) servers for SSL
[Thu Aug 25 15:19:43.850825 2016] [ssl:info] [pid 4275] AH01914:
Configuring server localho
If you add something like
LogLevel http2:debug
LogLevel ssl:debug
LogLevel core:debug
you should find information about negotiation in your error.log. Strange
that Firefox works and h2load does not. I use the later regularly in my tests.
Looking forward to see some log output...
> A
I am trying to do some benchmarking on different HTTP/2 webservers using
"h2load" from nghttp2.org.
I configured Apache with HTTP/2 and in wireshark I can see HTTP/2
traffic when connecting with a browser like firefox.
When I use h2load it falls back to HTTP/1.1 claiming the server does not
su
16 matches
Mail list logo
