[jira] [Commented] (OFBIZ-9224) 16.11 ofbizUrl include host+port and break some reverse-proxy / docker setups

["Jacques Le Roux (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OFBIZ-9224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874998#comment-15874998 ] 

Jacques Le Roux commented on OFBIZ-9224:
----------------------------------------

Thanks Leonard,

If nobody beats me on it, I'll have a look tomorrow afternoon (UTC)

> 16.11 ofbizUrl include host+port and break some reverse-proxy / docker setups
> -----------------------------------------------------------------------------
>
>                 Key: OFBIZ-9224
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9224
>             Project: OFBiz
>          Issue Type: Bug
>    Affects Versions: Release Branch 16.11
>            Reporter: Leonard Lin
>            Assignee: Jacques Le Roux
>
> OFBiz 16.11 has changed how it generates urls in its templates.
> It sometimes includes hostname+port.
> This can be reproduced on the official ofbiz-demo site:
> Go to http://ofbiz.apache.org/
> - Open the Ofbiz 13.07 Demo (Management Apps)
> - - it will auto-login for your, do a logout so that you can see the login-mask
> - - look at the HTML code and look for the form-post url etc. You can see that none of the URLs include hostname:port. They are all "/url/path"
> - Open the Ofbiz 16.11 Demo (Management Apps)
> - - it will auto-login for your, do a logout so that you can see the login-mask
> - - look at the HTML code and look for the form-post url etc.
> - - the post-urls and login-links have format: https://hostname:port/url/path
> The new 16.11 behaviour can cause problems in cluster / reverse-proxy setups where actual host:port does not match public host:port 
> Before 16.11 this was not an issue because all links were without hostname:port. But now the login masks loads but the subsequent links all show the wrong port.
> url.properties does control port/hostname but preferably we wouldn't need to configure it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)