1. Home
  2. Development
  3. RE: Liferay redirect from http to https not working correctly

RE: Liferay redirect from http to https not working correctly

Jamie Sammons, modified 2 Years ago.
Liferay redirect from http to https not working correctly
New Member Posts: 2 Join Date: 3/17/23 Recent Posts

I currently have a portal created with Liferay 7.1 and when I copy a url from http and paste it into the browser (converting it to https), it concatenates an extra /es/web in the url, so it does not find the resource and gives an error . Currently, in the configuration I have set the url to show the selected language (in this case 'es' from Spain) and also a /web. What can be happening? Is it a configuration issue of the portal itself?

I hope to find out if it is a Liferay configuration problem, that due to some parameter, it is concatenating these two words in an erroneous way or, it is a matter of the access server.

application security url redirections
thumbnail
Olaf Kock, modified 2 Years ago.
RE: Liferay redirect from http to https not working correctly
Liferay Legend Posts: 6441 Join Date: 9/23/08 Recent Posts

Please check where exactly the redirect is coming from.

Places to look at:

  • The browser's developer tools, network tab (is it a 301, 302 redirect?)
  • Is there a reverse proxy that might introduce some redirects? Specifically on the http->https redirects, there might be something off. Look at any rewrite/redirect rules configured there (or try to reproduce without the reverse proxy, to know on which side of the fence the problem is)
  • How is the reverse proxy configured? It might well introduce some extra path in there, which might be wrong
  • Do you have any custom code deployed that might introduce a redirection?
  • For completeness, but not for you (as you're on 7.1, where this is not yet available): Is there any redirection configured within Liferay itself?

Also, which exact​​​​​​​ version are you running? DXP? CE? Which GA release/fixpack? (make sure it's the latest available). Also consider upgrading to a current version (though that's not a short-term fix) - but you might want to try reproducing on the latest version without fully upgrading