I am running on Windows 19 Server.
Using the mod_proxy instead of ajp, works for me.
I also do not use ProxyPreserveHost
Something like this might work for you.
<VirtualHost *:80>
ServerName myserver.com
ServerAlias www.myserver.com
ProxyPass /server http://localhost:8080/server
ProxyPassReverse /server http://localhost:8080/server
</VirtualHost>
This should redirect myserver.com/server to http://localhost:8080/server.
If you want to redirect myserver.com to http://localhost:8080/server.
I think you would have to use
ProxyPass / http://localhost:8080/server
ProxyPassReverse / http://localhost:8080/server
But I'm not sure what you are trying to accomplish.
The subject line says 'how to add https support'.
But later in the thread you say you just want to 'proxy requests to
tomcat via reverse proxying'
- eric
On 2/7/2022 5:58 AM, Phillip jan wrote:
Hi! I am running on windows 10.
On Monday, February 7, 2022 at 9:38:25 PM UTC+8 Mark H. Wood wrote:
On Sun, Feb 06, 2022 at 08:48:07AM -0800, Phillip jan wrote:
> Hi! I am having issues with the backend installation,
particularly step 16.
> I don't know how to setup a virtualhost using https/port443
proxy to proxy
> all requests to apache and how to create an ssl certificate. I
am new to
> deploying a website in production environment. Can someone help
me? thanks
> in advance.
The details will depend on your operating system. Is this on Linux or
Windows? If Linux, what distribution (Ubuntu, Red Hat, etc.) and
version?
Some general notes:
o Virtual hosting and proxying are two separate issues. The proxy
connection will run within the virtual host.
o Proxying between Tomcat and HTTPD can be done using HTTP or AJP.
You need to choose one. The two services must both be configured
to agree on the details of their connection.
o Do you want to create a self-signed certificate, or obtain a
certificate from a certificate authority? Self-signed certificates
are easier and quicker to create, but will not be trusted by
browsers. They are useful for testing, or in closed environments.
A commercial or corporate certificate should be automatically
trusted within the scope of the authority which signed it. To make
your repository generally available, you will most likely want a
commercial certificate.
o It may be best to get these things working one at a time.
That is: first set up the virtual host and test that you can get
service from it with a simple static page. Then set up the proxy
connection and test that you can get service from DSpace. Then add
the certificate and set up HTTPS.
--
Mark H. Wood
Lead Technology Analyst
University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749 <tel:(317)%20274-0749>
www.ulib.iupui.edu <http://www.ulib.iupui.edu>
--
All messages to this mailing list should adhere to the Code of
Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/1a34d9dd-311d-4378-b0cb-447a9fbc10edn%40googlegroups.com
<https://groups.google.com/d/msgid/dspace-tech/1a34d9dd-311d-4378-b0cb-447a9fbc10edn%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/86642daf-b3cc-d0a3-6f0f-127e95816dea%40comcast.net.
