Score:0

Server

Can not access Tomcat servlet using httpd ajp proxy in Docker

Mirza Prangon

2/8/23, 9:45 AM

Docker, httpd and tomcat is new to me.

What I want to do: Access tomcat servlet through httpd ajp reverse proxy.

I am making two containers under same bridge network, one runs httpd, another tomcat.

Problem: I can not access tomcat through httpd. Httpd returns 403 error. I can access through port 8080 if I expose it to the host. I have read many articles but do not understand what I am doing wrong. Current configuration should work according to my understanding but surely I am missing something.

Screenshot of error page

Kindly give me pointers what am I doing wrong.

My configurations and dockerfiles Please see the Git repository here. I run the container by first creating image and run by following

# Start web container
docker run -dit --name httpd.container -p 80:80 --network extope-network httpd-101-image
# Start AP container
docker run -dit --name tomcat.container -p 8080:8080 --network extope-network --add-host=host.docker.internal:host-gateway tomcat-101-image

302

0 + 0

tomcat

mod-proxy

ajp

docker

apache-2.4

Gerald Schneider

2/8/23, 9:56 AM

The 403 error comes from tomcat, not httpd. Your httpd is working fine.

Mirza Prangon

2/8/23, 11:21 AM

Why would tomcat return 403 when accessed via httpd? As accessing by 8080 port works fine.

Gerard H. Pille

2/8/23, 11:29 AM

@GeraldSchneider, you may be mistaken, with the current configuration.

Score:0

Server

Gerald Schneider

2/8/23, 12:04 PM

Remove the quotes from the secret in your httpd config.

ProxyPass "/docs" "ajp://tomcat.container:8009/docs" secret=test_ajp_secret
ProxyPass "/manager/" "ajp://tomcat.container:8009/manager/" secret=test_ajp_secret

Afterwards it works.

0 + 0

Mirza Prangon

2/12/23, 2:27 AM

This actually solved my problem! The documents can be more clear in this regards saying to not to use double quotes.

Score:0

Server

Gerard H. Pille

2/8/23, 11:01 AM

Your server.xml redirects traffic to port 8443, but,

doesn't handle that port (the handler is commented out)
the container doesn't accept traffic for that port.

In the httpd.conf I see "Include conf/httpd_extope.conf", but there is no httpd_extope.conf. The http_proxy.conf tries to contact the container on port 8009, for which the above two remarks are also valid.

0 + 0

Mirza Prangon

2/8/23, 11:15 AM

Thank you, I tried removing redirect port line on ajp connector, but the problem persists. By the way, in the connector configuration for 8080 port, there is also a line for redirection to same 8443 port, but i am able to access through 8080 port. Why is that?

Gerard H. Pille

2/8/23, 11:28 AM

Port 8080 is handled correctly. See another problem you have above.

Mirza Prangon

2/8/23, 11:34 AM

Sorry i changed the file names before sharing. The file names are correct in my environment. I will fix that

Gerard H. Pille

2/8/23, 12:05 PM

That doesn't change the problem with port 8009.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Can not access Tomcat servlet using httpd ajp proxy in Docker

TH: ไม่สามารถเข้าถึง Tomcat servlet โดยใช้ httpd ajp proxy ใน Docker

RO: Nu se poate accesa servletul Tomcat folosind proxy httpd ajp în Docker

RU: Не удается получить доступ к сервлету Tomcat с использованием прокси-сервера httpd ajp в Docker

VI: Không thể truy cập servlet Tomcat bằng proxy httpd ajp trong Docker

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.