nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Redirect on runtime

rvanbent

Hi,
Does anybody know an 'easy' way to introduce redirects on request URI on the LiveSite Runtime?

Example: www.webaddress.com goes to basic LiveSite site
www.webaddress.com/**** has to go to an external webapplications
www.webaddress.com/yyy has to go to another external location

I'm trying to get InvalidSites.jsp to do it for me but I can't seem to get the provided uri input.

Cheers
Robert

Find more posts tagged with

Comments

Crsb

once you hit InvalidSite.jsp, you already lost the original request uri.

check out this file LiveSiteDisplayServices/runtime/web/WEB-INF/urlrewrite.xml it might have what you need, if you might have to change to .

rvanbent

Don't have that one, just web.xml and weblogic.xml. No sight of urlrewrite.xml. Running 7.2.1 on Win2008.
So I created one with the basic in it, still doesn't work.

kamalesh

Ideally you should detect this at the web server level and redirect to your external sites.

rvanbent

Yes Kam, that would be ideal but where is that on the runtime site?

Migrateduser

@rvanbent -> Ideally your runtime would be installed on an App server, the requests to which are tunneled through an HTTP server. In many cases, the app server acts as the web server too.

So i am just trying to understand what you imply here by " but where is that on the runtime site"

RonaldV

Hi Robert,

how are you. Still in living in Sydney,are you?

Normally, in a prod-env you would have a webwerver (apache, iis) be in front at port 80. This webserver would pass all livesite requests on to the app-server (like tomcat, jboss). But requests for non-livesite content would better/faster be served by the webserver directly.

Now, on a dev (???) environment on which I assume you are there is no webserver in front of tomcat. It is just the webserver inside tomcat (port 1776?) the listens to you request.

So in this case you could either:
- configure tomcat to route /**** to your external web-app via the web/server.xml
- hack the invalidsite.jsp
- add a filter that will catch and reroute your request for /****

Hope this helps.

rvanbent

@ he Ronaldo, yes still in sunny Sydney. We have a bit of a slim down version of the whole install here and we are running straight at the Tomcat server with our production websites. No extra webserver in front (planned for later)
We have tried to alter web/server.xml with not much success yet.
Hacking invalidsite.jsp doesn't work for a request to the root (which presents the wrong site at the moment) and doesn't have the information from the initial request as 'Crsb' mentioned. His urlrewrite.xml is not available at LSDS so I'm wondering if anybody ever thought of rewriting urls straight at the LSDS source. Probably not.

@bmazum
What I mean with " but where is that on the runtime site" is which configuration file much I change to do rewrites of url requests on LSDS.
We have Tomcat/Apache LiveSite Runtime out of the box vanila install running as our jolly websites host.