changing the context path

[marwan amin sabri, modificado hace 7 años.]

Dears,

I was successfully able to change my default context path to be http://mydomain/webportal
but unfortunately my Portlets and my themes are not able to generate the path into the css and js files, links are pointing to http://mydomain/myportlet/css directly which is out of my context!


Any idea how to solve it?

Marwan Alsabri

[Gautam Sharma, modificado hace 7 años.]

This might help you https://web.liferay.com/community/forums/-/message_boards/message/5908320

[marwan amin sabri, modificado hace 7 años.]

Dear Gautam,

Thanks for your promote answer, indeed this works for my theme, but for the portlet it doesn't work even if use the same attribute in the portlet conf file.

[Mika Koivisto, modificado hace 7 años.]

When you change the context of the portal you are only changing the context of the core and the portlets still have their own context. What you might be looking for is the property portal.proxy.path but with that you'll need a frontend proxy that proxies to the real path. Here's the doc from portal.properties:

#
# Set this property if the application server is served behind a proxy and
# a prefix needs to be added to the portal servlet context path. This prefix
# will also be added to static resources served by layout templates,
# portlets, and themes.
#
portal.proxy.path=

[marwan amin sabri, modificado hace 7 años.]

Thanks Mikaib

in fact i do have IBM TAM and IBM reverse proxy in front of my server also i've configured TAM conjunctions to by pass all requests with /webportal ,your solution will make all my links going to the same URL and i might have double entry for the portlet like /webportal/webportal/

have u faced such case before?

[Gautam Sharma, modificado hace 7 años.]

It means now you have issue with only portlet,not with theme please correct me if i am wrong.

Just wanted to check if you have done anything on webserver to prevent access apart from theme.