[mashup-dev] [jira] Commented: (MASHUP-26) Redirect of localhost to
non-existant endpoint
Thilina Gunarathne (JIRA)
jira at wso2.org
Mon Jun 4 09:20:02 PDT 2007
[ http://www.wso2.org/jira/browse/MASHUP-26?page=comments#action_11080 ]
Thilina Gunarathne commented on MASHUP-26:
------------------------------------------
Earlier WSAS was using the host name(always the prominent IP), port & service context sent by the server side to perform the service calls. Now we decided to use the host address obtained from the browser to call the backend services.
So when the user types "localhost" in the address bar of the browser, the js file would be retrieved from the "localhost". Then all the service calls will be made to the "http://localhost:port//services/....." without having to warry about the SOP...
> Redirect of localhost to non-existant endpoint
> ----------------------------------------------
>
> Key: MASHUP-26
> URL: http://www.wso2.org/jira/browse/MASHUP-26
> Project: WSO2 Mashup Server
> Issue Type: Bug
> Environment: Nightly build 5/10
> Reporter: Jonathan Marsh
> Assigned To: Thilina Gunarathne
> Priority: Critical
> Fix For: alpha_1
>
>
> When accessing a service through http://localhost a 302 redirect is returned. I presume the framework will retry the request at that address. But the address returned is https://xx.xx.xx.xx:9443/ which is not a live endpoint.
> Maybe this is as simple as having a correct endpoint address returned would solve the problem - or to deploy an https endpoint by default.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the Mashup-dev
mailing list