This would totally break our apps! :)
If you truly are pondering this, figure out if there is an easy way to
reverse this feature :) At least until we can figure out how to handle
it properly on our end. :)
The problem is that because of facebook proxies, we have to in a lot of
places make the urls absolute. so we're doing stuff like
"${baseurl}${creatlink}".
Howard M. Lewis Ship (JIRA) wrote:
> [
> https://issues.apache.org/jira/browse/TAPESTRY-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Howard M. Lewis Ship reassigned TAPESTRY-1502:
> ----------------------------------------------
>
> Assignee: Howard M. Lewis Ship
>
>> Generated URLs should be relative to request base URL
>> -----------------------------------------------------
>>
>> Key: TAPESTRY-1502
>> URL: https://issues.apache.org/jira/browse/TAPESTRY-1502
>> Project: Tapestry
>> Issue Type: Improvement
>> Components: tapestry-core
>> Affects Versions: 5.0
>> Reporter: Howard M. Lewis Ship
>> Assignee: Howard M. Lewis Ship
>> Priority: Minor
>>
>> When Tapestry generates a URL to render a page, invoke an action, or
>> download an asset, it always builds a complete path, i.e.,
>> "/context/foo/bar". In many cases, the links from the current rendered page
>> (which establishes a base URL) to other resources would be shorter and more
>> readable if relative. This if you are rendering page "users/edit" (i.e. at
>> URL "/context/users/edit") and submit a form, the URI would be "edit.form"
>> not "/context/users/edit.form").
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
