testbed configuration

[Kevin Buckley]

On 2023/09/04 17:12, Dave Perry via users wrote:
> On 2023/09/04 17:09, Peter Schober via users wrote:
>>> I also have a front-end Apache server, listenting on 443, that
>>> proxies into the Jetty instance.
>> 
>> Again trying to help simplify this excersise: Why add httpd and
>> proxing at all? Jetty can also serve as an TLS-enabled web server.
>> (You could even drop TLS for now if this is merely a test.)
>> 
>>> [proxy_ajp:debug]  [pid 14908:tid 14] mod_proxy_ajp.c(769):     [client 192.168.56.1:41458] AH00895: serving URL ajp://localhost:8080/idp/profile/admin/hello
>> 
>> I'm not aware recent Jetty versions even supported AJP?
>
> Backing you on both points Peter.
> 
> Our prod and test instances run Jetty as the sole service, with
> the same config around entityID and URLs (barring changes I'm
> testing, eg the Azure Proxy thing atm). 

Thanks both,

I did, initially, not have an Apache server in front of things,
however, my initial attempts to set things up with just Jetty,
didn't see me make all that much progress, but it now seems that
because (httpd+proxy+servlet container) is the way I had deployed
things back in the v2 days, I am carrying a bit of historical
baggage with me.

I will be labelling said baggage "not wanted on voyage" asap.

Thanks again for steering the ship back on course,
Kevin Buckley