| Wrong context path since 3.0 or 3.1 [message #1730514] |
Tue, 26 April 2016 09:17  |
Eclipse User |
|
|
|
Hi guys,
the ServiceManagerImpl.getServiceHandlerUrl() ist returning the wrong context path.
We have a proxy rewrite and the hole path to our entry point is cutted.
Before/correct (2.3): http://ourdomain.org/path1/path2/entrypoint?...
Now/wrong (3.1): http://ourdomain.org/entrypoint?...
This will destroy the functionallity of all using
RWT.getServiceManager().getServiceHandlerUrl( SERVICE_ID )
So upload/download and so on...
I don't know why and when this is done wrong in the RAP code base, but with 2.3 it was working...
My presentation is tomorrow, so any help is highly appreciated!
~Ingo
[Updated on: Tue, 26 April 2016 09:18] by Moderator |
|
|
|
|
|
| Re: Wrong context path since 3.0 or 3.1 [message #1741598 is a reply to message #1730514] |
Fri, 26 August 2016 04:42  |
| Eclipse User |
|
|
|
Hi RAP team,
it seems like there is another setup the current implementation of RWT.getServiceManager().getServiceHandlerUrl does not cover yet:
A customer deployed an application on a server with an entry point like someserver/myEntryPoint (in the internal network). Public access is provided via a subdomain, e.g. theapp.mydomain.com which obviously redirects to someserver/myEntryPoint.
Calling getServiceHandlerUrl currently returns /myEntryPoint/?servicehandler=xxx ... - which results in the url theapp.mydomain.com/myEntryPoint/?servicehandler=xxx ... on the client side.
After the sub domain redirect the final url appears to be someserver/myEntryPoint/myEntryPoint/?servicehandler=xxx ... which does not exist. I am not really familiar with sub domain configuration, but I think this is what happens.
Unfortunately, the system property that has been introduced with the fix for bug 492175 does not help at all, since the context path is added to the result of getServiceHandlerUrl in any case. So my first thought was that the context path should not be added to the result of getServiceHandlerUrl when "org.eclipse.rap.rwt.serviceHandlerBaseURL" is set. Instead, it might be part of the base url configured in that property (if it is required).
It's probably possible to fix this with url rewriting on the server side or even by removing the entry point from the returned url in the code (which would not be nice); however, I think this is not such an uncommon setup and the framework should provide respective configuration to not bother administrators with web application specific extra configuration.
Hope, I did not miss anything essential here. What do you think?
Regards,
Sebastian
[Updated on: Fri, 26 August 2016 04:44] by Moderator |
|
|
Powered by
FUDForum. Page generated in 0.38146 seconds
Home