You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Nguyễn Việt Đức (Jira)" <se...@james.apache.org> on 2020/07/28 08:32:00 UTC
[jira] [Commented] (JAMES-3347) Configure session hardcoded
prefixes
[ https://issues.apache.org/jira/browse/JAMES-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166258#comment-17166258 ]
Nguyễn Việt Đức commented on JAMES-3347:
----------------------------------------
duplicated https://issues.apache.org/jira/browse/JAMES-3316
> Configure session hardcoded prefixes
> ------------------------------------
>
> Key: JAMES-3347
> URL: https://issues.apache.org/jira/browse/JAMES-3347
> Project: James Server
> Issue Type: Improvement
> Reporter: Nguyễn Việt Đức
> Priority: Major
>
> # WHY
> In *SessionSupplier.scala*:
> {code:java}
> apiUrl = new URL(s"$HARD_CODED_URL_PREFIX/jmap"),
> downloadUrl = new URL(s"$HARD_CODED_URL_PREFIX/download"),
> uploadUrl = new URL(s"$HARD_CODED_URL_PREFIX/upload"),
> eventSourceUrl = new URL(s"$HARD_CODED_URL_PREFIX/eventSource")))
> {code}
> We hard coded with a costant the URL prefix for JMAP service endpoint advertised via the session object.
> This of course should be adapted to the running server domain/URL
> # How
> We should be able to parse and configure this prefix reading `jmap.properties`
> **DOD** We should be able to get HARD_CODED_URL_PREFIX from JMAP server configuration.
> Write (or adapt) an integration test where the session route relies on the configured parameters.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org