Dear Mr. Schultz:
Delighted to hear from you, and delighted that you weighed in on this.
You've already earned my undying respect and gratitude. This also allows
us to drop one more cert that we have to pay for, and I think it could
lead to an easy way to drop yet another.
On 4/9/20 3:31
On 4/9/20 1:37 PM, Peter Kreuser wrote:
It should be sufficient to just do a Location directive and then Require.
Require
Dear Herr Kreuser:
Thanks. I was beginning to wonder if Location might be the answer.
--
JHHL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 4/6/20 15:53, James H. H. Lampert wrote:
> Here is the situation:
>
> We have an existing Amazon EC2 instance, running Amazon Linux 2,
> with an Apache httpd server already running our web sites (for
> argument's sake, "foo.com,"
Mark, James
> Am 09.04.2020 um 22:14 schrieb Mark Eggers :
>
> James,
>
>> On 4/9/2020 12:11 PM, James H. H. Lampert wrote:
>>> On 4/6/20 2:13 PM, Mark Eggers wrote:
>>> # Secure your proxy - localhost for now - this is IMPORTANT
>>>
>>>Require ip 127
>>>
>>
Isn‘t this for CONNECT
James,
On 4/9/2020 12:11 PM, James H. H. Lampert wrote:
> On 4/6/20 2:13 PM, Mark Eggers wrote:
>> # Secure your proxy - localhost for now - this is IMPORTANT
>>
>> Require ip 127
>>
>
> Dear Mr. Eggers:
>
> It seems I was right about how what you said about this, and what the
> docs say
On 4/6/20 2:13 PM, Mark Eggers wrote:
# Secure your proxy - localhost for now - this is IMPORTANT
Require ip 127
Dear Mr. Eggers:
It seems I was right about how what you said about this, and what the
docs say about it, appeared to contradict each other: with that in the
VirtualHost
On 4/8/2020 6:42 PM, calder wrote:
> On Wed, Apr 8, 2020, 18:11 James H. H. Lampert
> wrote:
>
>>
>> And as to vendor-supplied installations, I agree with you. I'm rather
>> irritated with the "Debianism" of splitting Tomcat up so completely that
>> webapp contexts can be in at least two
On Wed, Apr 8, 2020, 18:11 James H. H. Lampert
wrote:
>
> And as to vendor-supplied installations, I agree with you. I'm rather
> irritated with the "Debianism" of splitting Tomcat up so completely that
> webapp contexts can be in at least two different places, and the general
> "Linuxism" of
James,
On 4/8/2020 5:41 PM, James H. H. Lampert wrote:
> On 4/8/20 4:57 PM, Mark Eggers wrote:
>> See
>> https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxy
>> for some examples.
>
> Yes. That's the very point in the documentation that has my head spinning:
>>> For example, the following
On 4/8/20 4:57 PM, Mark Eggers wrote:
See
https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxy
for some examples.
Yes. That's the very point in the documentation that has my head spinning:
For example, the following will allow only hosts in
yournetwork.example.com to access content via
On 4/8/2020 4:11 PM, James H. H. Lampert wrote:
> On 4/8/20 3:52 PM, Mark Eggers wrote:
Require ip 127
>
> Dear Mr. Eggers (et al.):
>
> I'm still not clear on what that even *does* (and the official docs
> leave me even more confused: "only allow hosts in . . . to access
>
On 4/8/20 3:52 PM, Mark Eggers wrote:
Require ip 127
Dear Mr. Eggers (et al.):
I'm still not clear on what that even *does* (and the official docs
leave me even more confused: "only allow hosts in . . . to access
content via your proxy"); could you (or somebody else) explain it?
James,
On 4/8/2020 3:27 PM, James H. H. Lampert wrote:
> Dear Mr. Eggers, et al.:
>
> Well, after running test installations of Tomcat on a whole string of
> EC2 spot instances, I went ahead and installed it on the target server.
> I've got it running, and enabled to start automatically, and
Dear Mr. Eggers, et al.:
Well, after running test installations of Tomcat on a whole string of
EC2 spot instances, I went ahead and installed it on the target server.
I've got it running, and enabled to start automatically, and I've added
a security group to temporarily open 8080 to my office
I don't have enough reputation points to comment on your question on
serverfault.
Is your DocumentRoot (/var/www/html/test) underneath the default
DocumentRoot (normally /var/www/html)?
I found the problem, and it wasn't a [profanity] server problem; it was
a [profanity] client problem!
On 4/6/2020 5:47 PM, James H. H. Lampert wrote:
> As it happens, I'm now struggling with an issue just trying to get a new
> virtual host up and running on the httpd server. I've put it on Server
> Fault, at: https://preview.tinyurl.com/rr3rxwa
>
> While it may not be necessary to solve this
As it happens, I'm now struggling with an issue just trying to get a new
virtual host up and running on the httpd server. I've put it on Server
Fault, at: https://preview.tinyurl.com/rr3rxwa
While it may not be necessary to solve this problem in order to get the
httpd server to proxy the
James,
On 4/6/2020 3:09 PM, James H. H. Lampert wrote:
> First of all, thank you, Mr. Malcom, Herr Kreuser, and Mr. Eggers.
>
> One thing I will note is that near as I can tell, mod_proxy and
> mod_proxy_http are already present on the system (I can find
> "mod_proxy.so" and
First of all, thank you, Mr. Malcom, Herr Kreuser, and Mr. Eggers.
One thing I will note is that near as I can tell, mod_proxy and
mod_proxy_http are already present on the system (I can find
"mod_proxy.so" and "mod_proxy_http.so"), but mod_jk does not appear to
be present (no sign of a
Hi Jerry / James,
On 4/6/2020 1:59 PM, Jerry Malcolm wrote:
> Hi James,
>
> I've been using this precise setup for years, first on a dedicated
> hosted server and recently on EC2/Linux2. I use mod_jk.
>
> The first step is to make sure httpd recognizes all of the domain names
> and subdomains.
James,
On 4/6/2020 12:53 PM, James H. H. Lampert wrote:
> Here is the situation:
>
> We have an existing Amazon EC2 instance, running Amazon Linux 2, with an
> Apache httpd server already running our web sites (for argument's sake,
> "foo.com," "bar.com," and "baz.com."), and already getting its
Hi James,
I've been using this precise setup for years, first on a dedicated
hosted server and recently on EC2/Linux2. I use mod_jk.
The first step is to make sure httpd recognizes all of the domain names
and subdomains. That includes the vhost definitions of all of the
domains and
James,
> Am 06.04.2020 um 21:53 schrieb James H. H. Lampert :
>
> Here is the situation:
>
> We have an existing Amazon EC2 instance, running Amazon Linux 2, with an
> Apache httpd server already running our web sites (for argument's sake,
> "foo.com," "bar.com," and "baz.com."), and already
Here is the situation:
We have an existing Amazon EC2 instance, running Amazon Linux 2, with an
Apache httpd server already running our web sites (for argument's sake,
"foo.com," "bar.com," and "baz.com."), and already getting its certs
from Let's Encrypt, using "foo.com" as the CN, with
24 matches
Mail list logo
