Apache :: redirect to same server but with additonal parameters in URL

guthrie · Joined: 29 Jun 2019 Posts: 5 Location: usa, fairfield

I have a cloud server site at a fixed IP address ("Site") and have a domain name "CS" that points to it. I did this just to isolate the public name (CS) from the current server (Site) used.
On that system I setup a server tool that is accessed by the URL: "CS:8000/index".
I created an additional domain name to hide those details, "TmR", and want to have TmR map to "CS:8000/index".
I then added a new virtual server on CS(=> Site) like this:

tangent · Moderator Joined: 16 Aug 2020 Posts: 348 Location: UK

In your post you say you set up the "TmR" site to hide the details of the CS site details, so believe you need to use proxy directives rather than redirects, else the browser will switch to CS based URLs.

However, you don't say whether the missing css (and other support files) are relative to the CS site root or below the index suffix you've specified. If they are below, then your proxypass paths will need to match, and you'll probably want a redirect from the site root to /index, e.g.

guthrie · Joined: 29 Jun 2019 Posts: 5 Location: usa, fairfield

Thank you for the note and reply.
If I run this:
Tmr:8000/index
it works fine, as before.
but just running Tmr (with your setup)
converts it to:
CS:8000/Index
which gives a 404 error, although the browser tab shows the Tmr app icon (I don't know how that is set).
(I simplified the actual URL which is:
http://Tmr:8000/index.php/ojs-files/index )

guthrie · Joined: 29 Jun 2019 Posts: 5 Location: usa, fairfield

Hmm,
plain: tmr
fails, but running tmr:8000
resolves fine and runs
It resolves to tmr:8000/Index...
which has always been working.

tangent · Moderator Joined: 16 Aug 2020 Posts: 348 Location: UK

There's not enough detail here to work out exactly what's going on.

Suggest you use Developer Tools in your browser (Ctrl+Shift+I) to check on exactly what Request/Response Headers are occurring, along with the Response Body, and from that determine what changes are needed to your Apache configuration and site content.

guthrie · Joined: 29 Jun 2019 Posts: 5 Location: usa, fairfield

ok.
Also, for example, the direct IP, gives an non-terminating redirect...
It should just get the standard :80 welcome web page, as should /CS alone.
159... -> 159..../indexindexindexindexindex...

tangent · Moderator Joined: 16 Aug 2020 Posts: 348 Location: UK

So is /index a folder or a file? If a file is your site entry point index.html or index.php (a previous post suggested index.php was a folder:- http://Tmr:8000/index.php/ojs-files/index)?

If /index is a folder, then change the redirect to match, e.g. /index/

If your entry point is index.php, have you updated the DirectoryIndex entry to include index.php?

If you're still stuck, suggest you post your configuration (anonymized) to pastebin along with an overview of your site content layout, so people may be able to help you further.

guthrie · Joined: 29 Jun 2019 Posts: 5 Location: usa, fairfield

Thank you.
I think that index is a file - but since this system runs on a php web-server (:8000) I don't know the details of how that works, or is configured.
I think the Apache URL (Tmr:80) is supposed to hand off the request to the PHP server (:8000/Index (=Params)), which is configured for it's own "index" file configuration.
If I can just get that redirection setup, then I don't need to know how the self-contained php server and setup works.
And as noted, if I give the full URL to it directly it does work find, so I am just fighting with Apache to do the remapping of the URL.
I'll research further.