[INTPAK-152] Enabling TLS does not explicitly disable HTTP REST Created: 20/Mar/18  Updated: 22/May/18  Resolved: 22/May/18

Status: Closed
Project: integration-packaging
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Highest
Reporter: Tim Rozet Assignee: Tim Rozet
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

We configure pax HTTP port to be the same as HTTPS port.  Previously this worked and only HTTPs would come up.  However with changes to Oxygen this now is seen as a port conflict by Pax and REST fails to come up at all.  The solution is to explicitly disable http when TLS is enabled via Pax config.  Also, there is a duplicate configuration for http port in the pax config file due to  a missing regex match when setting the file_line.



 Comments   
Comment by Tim Rozet [ 22/May/18 ]

Change 69699 - Merged
 
Reply… 
 
Included in
Patch Sets (2/2)
Download
 

INTPAK-152 Disable HTTP when TLS is enabled There are port conflicts when TLS is enabled due to HTTP and HTTPS starting on the same port. Changes-Include: - Explicitly disables HTTP when TLS is enabled - Fix missing match on HTTP Pax port - Only configuring HTTP pax port when TLS is not enabled Change-Id: Ie077c9ff7edeb34c91186ca1f492d607f0e55cc4 Signed-off-by: Tim Rozet <trozet@redhat.com> Signed-off-by: Daniel Farrell <dfarrell@redhat.com>
Generated at Wed Feb 07 20:03:45 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.