[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21220#action_21220
]
Gregory Joseph commented on MAGNOLIA-2610:
------------------------------------------
That is exactly what I meant ;) But by looking at the current implementation,
the only "simple" way of solving this was by adding an extra property to pass
between MgnlServletContextListener and PropertiesInitializer.
> always use unqualified server names in properties resolution
> ------------------------------------------------------------
>
> Key: MAGNOLIA-2610
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2610
> Project: Magnolia
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.0 M2
> Reporter: Fabrizio Giustina
> Assignee: Fabrizio Giustina
> Fix For: 4.1
>
>
> The server name resolved in MgnlServletContextListener.initServername() is
> usually a not qualified hostname ("hostname" and not "hostname.domain.com"),
> but sometimes seems that InetAddress.getLocalHost().getHostName() can also
> return a fully qualified hostname with the domain (not really sure about the
> logic behind it, I've seen different behaviour on similarly configured linux
> machines).
> I think it will be better to always force an unqualified hostname, so that
> the behavior is more predictable...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
