Commented Unassigned: Composite.Tools.LegacyUrlHandler on site with multiple hostnames [2105]

When I run /StoreCurrentPaths.aspx on a site with multiple hostnames I get a list where pages on the current site is listed without hostname (like /mypage) and pages on the other sites is listed with hostname (like http://www.contoso.com/mypage).
Is this intended?
Do I have to run /StoreCurrentPaths.aspx from all hostnames?
Comments: ** Comment from web user: wysocki **

Logged in TFS as Issue 4888

__Repro steps__:

1. Have a setup with 2+ websites in one installation
2. Map each website to its own hostname: e.g., website1.com and website2.com
3. Access and run the store paths functionality from one of the websites: http://website1.com/StoreCurrentPaths.aspx
4. Check ~/App_Data/LegacyUrlMapping.xml

__Expected__: old paths are specified with hostnames for both websites

```
<Mapping OldPath="http://website1.com/Page-1" NewPath="~/page(53cb31ee-85ff-4315-8f0d-6c5fdd1378ea)" />
...
<Mapping OldPath="http://website2.com/Page-1" NewPath="~/page(3c28a8e2-bb16-4907-99fd-1b74989a3ab9)" />
```

__Actual__: old paths for the current website (website1.com) are specified without its hostname, for the other website (website2.com) - with its hostname

```
<Mapping OldPath="/Page-1" NewPath="~/page(53cb31ee-85ff-4315-8f0d-6c5fdd1378ea)" />
...
<Mapping OldPath="http://website2.com/Page-1" NewPath="~/page(3c28a8e2-bb16-4907-99fd-1b74989a3ab9)" />
```