[
https://issues.apache.org/jira/browse/ASYNCWEB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard updated ASYNCWEB-13:
--------------------------------------
Attachment: patch-ASYNCWEB-13.txt
Due tu current problem with ASF SVN server, here a patch to apply to last
asyncweb-server module.
ift's adding a getLocalAddress() to HttpServiceContext
> No possibility to determine server socket in HttpService
> --------------------------------------------------------
>
> Key: ASYNCWEB-13
> URL: https://issues.apache.org/jira/browse/ASYNCWEB-13
> Project: Asyncweb
> Issue Type: Improvement
> Components: Server
> Environment: AsyncWeb 0.9.0-CVS
> Reporter: Daniel Wirtz
> Assignee: Julien Vermillard
> Attachments: patch-ASYNCWEB-13.txt
>
>
> I cannot find a possibility to get the server socket's address from a
> HttpContext object, but a method to get the remote address is present.
> FastCGI (in this particular case FCGIHttpService) depends on this information
> for inclusion in the protocol specific SERVER_ADDR and SERVER_PORT parameters.
> public void handleRequest(HttpServiceContext context) throws Exception {
> ...impossible to determine the server socket address on which the request
> came in to send it with a fastcgi request....
> }
> Of course it could be manually set within the HttpService's constructor each
> time, but when a server listens on more than one address, it will not suffice.
> A solution would be to add a getLocalAddress() (similar to the already
> existing getRemoteAddress()) method to the HttpContext.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
