Hello, i am searching for a special solution - i try to explain what i want to realize - hopefully fo get feedback, if this is possible - and support in setting up ... at least, somebody who can help with "hands" on on a professional level.
Currently i have the standard hosting with domain and standard dns setting with nameservers on hosting platform (i am able to set domain settings as well as i can set a complete external nameserver.
Now the plan is the following:
We would like to set up a reverse proxy for our domain (example domain we name here abc.com).
Here is what we need:
- If someone visits abc.com (just the main domain), they should be redirected to the homepage on an external server.
- If someone visits abc.com/ziel1 or abc.com/ziel2, they should be redirected to specific target URLs that we can manage.
- If someone visits any other path (for example, abc.com/anything-else), the request should also be passed unchanged to the external server.
In short:
Only the main domain and specific paths should be redirected. All other requests should be forwarded unchanged to the external server - homepage of that domain.
Currently the idea would be to set up a "droplet" . a small server at digitalocean.com and create the hosting, install openLiteSpeed and configure the basic redirections ... and later i can add the more individual links as needed.
Is it correct, that litespeed has a visual gui, were it is possible to create new redirect-links on that gui without developing knowledge?
Thank you very much for your feedback.
Currently i have the standard hosting with domain and standard dns setting with nameservers on hosting platform (i am able to set domain settings as well as i can set a complete external nameserver.
Now the plan is the following:
We would like to set up a reverse proxy for our domain (example domain we name here abc.com).
Here is what we need:
- If someone visits abc.com (just the main domain), they should be redirected to the homepage on an external server.
- If someone visits abc.com/ziel1 or abc.com/ziel2, they should be redirected to specific target URLs that we can manage.
- If someone visits any other path (for example, abc.com/anything-else), the request should also be passed unchanged to the external server.
In short:
Only the main domain and specific paths should be redirected. All other requests should be forwarded unchanged to the external server - homepage of that domain.
Currently the idea would be to set up a "droplet" . a small server at digitalocean.com and create the hosting, install openLiteSpeed and configure the basic redirections ... and later i can add the more individual links as needed.
Is it correct, that litespeed has a visual gui, were it is possible to create new redirect-links on that gui without developing knowledge?
Thank you very much for your feedback.
) I did a bit of reading up and it wasn't advised to try and change any settings if it was set as read only as OLS can be very temperamental. I opted to go back to Apache on that occasion but I do plan on learning more about the nuts and bolts of OLS.