[
https://issues.apache.org/jira/browse/TAP5-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703762#action_12703762
]
Howard M. Lewis Ship commented on TAP5-286:
-------------------------------------------
I don't think this will make it for 5.1 but it's still a good idea. You can
kind of cobble together a solution today, but it would be nice if it was a
switch. At issue is the fact that, when behind a proxy server, Tapestry will
not be able to determine the base URL on its own.
> Add the possibility (as an option) for all generated URL to include the
> domain and context
> ------------------------------------------------------------------------------------------
>
> Key: TAP5-286
> URL: https://issues.apache.org/jira/browse/TAP5-286
> Project: Tapestry 5
> Issue Type: New Feature
> Affects Versions: 5.0.16
> Reporter: Martin Papy
>
> Now that we have the possibility to access the Dom and manipulate it easily,
> we can use Tapestry to generate email based on Page Rendering... But Tapestry
> generate only absolute URL ( without http://mydomain.com/context/ ).
> For the moment I do this in the cleanupRender phase :
> String mailBody = writer.getDocument().getRootElement.toString();
> And I send the result by mail.
> It would be very useful if we could tell Tapestry -maybe with a special
> Annotation- that we want for a particular Page/Component all URL / Link to
> pages / Link to Assets (and so on) to be fully qualified ( ie not
> /assets/xxxx/yyy.jpg but http(s)://domain.com/context/assets/xxxx/yyy.jpg )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
