default "server.xml", the lines are as follows:
The new section should look like:
8. Start the Control-M Web Server
On Fri, Feb 24, 2017 at 8:29 AM, Aaron Gray wrote:
> Andre, that is all very educational and I feel even when this is resolved,
> that I ha
; "Location:" header that is in that redirect response would be properly
> edited before returning that redirect response back up the chain, in such a
> way that the ultimate client would not try next, to access a URL that leads
> nowhere.
>
> And now it's really late
of this is an issue if you dont hit it with the F5 Load
Balancer to start.
On Thu, Feb 23, 2017 at 10:24 AM, Aaron Gray wrote:
> I randomly tried https://loadbalancer.domain.com/SelfService/index.html
>
> It works perfectly. No issues. I have no idea why its needed to add on
> the
e
url rewrite or something, IF this cant be fixed normally?
On Thu, Feb 23, 2017 at 10:10 AM, Aaron Gray wrote:
> Okay, guys, please accept my most sincere apology on this thing. I just
> figured 1 thing out.
>
> browser -> f5:443 -> httpd (23270, https) -> tomcat (http)
>
i dont know these things. I
know they told me it is HTML5, as it was using Silverlight back in the
older release.
On Thu, Feb 23, 2017 at 9:22 AM, Aaron Gray wrote:
> Working with my F5 guy, we had an idea, since 80/tcp and 443/tcp were
> already open to the VIP on the F5, we simply turne
to the HTTP Server and slip
the F5. And F5 works landing the /healthcheck.html (HTTP KeepAlive in the
root, which isnt proxied), so all good there. Just cant /SelfService
(configured w/ Proxy)
thanks for your support here though.
On Thu, Feb 23, 2017 at 9:12 AM, Aaron Gray wrote:
> SS
firewall to be opened, which is
not able to open until 3/2. Gonna see.
On Thu, Feb 23, 2017 at 8:22 AM, Antonio S. Cofiño
wrote:
>
> On 23/02/17 12:43, André Warnier (tomcat) wrote:
>
>> On 22.02.2017 19:22, Aaron Gray wrote:
>>
>>> So this is interesting.
>>>
1, 2017 at 3:39 PM, André Warnier (tomcat)
wrote:
> On 21.02.2017 23:28, Aaron Gray wrote:
>
>> Antonio: The Tomcat server has no knowledge of the F5, or that it is
>> being
>> fronted by an Apache HTTP Server. I do SSL termination in Apache HTTP
>> Server, and cle
the finger elsewhere, which will
make this an even bigger hassle.
On Tue, Feb 21, 2017 at 3:39 PM, André Warnier (tomcat)
wrote:
> On 21.02.2017 23:28, Aaron Gray wrote:
>
>> Antonio: The Tomcat server has no knowledge of the F5, or that it is
>> being
>> fronted
nnel. Therefore the non-confidential to the 18080 port from the
> balancer are redirected to the 23270 port, but it should be 443.
>
> Antonio
>
>
>
> El 21/2/2017 19:46, "Aaron Gray" escribió:
>
> I have an application server from a vendor that comes bundled
I have an application server from a vendor that comes bundled with an
additional Apache Tomcat server. The webapp SelfService.war is vendor
supplied too.
Here's my problem (IP's replaced to protect the innocent):
networks:
DMZ=172.x.x.x
INTERNAL=10.x.x.x
server1 https listen = 172.1.1.1:23270
s
11 matches
Mail list logo
