Created: (ASYNCWEB-13) No possibility to determine server socket in HttpService

Thread: Created: (ASYNCWEB-13) No possibility to determine server socket in HttpService

Search this list only Search all lists
Created: (ASYNCWEB-13) No possibility to determine server socket in HttpService
United States	2008-04-25 12:27:56
No possibility to determine server socket in HttpService -------------------------------------------------------- Key: ASYNCWEB-13 URL: htt ps://issues.apache.org/jira/browse/ASYNCWEB-13 Project: Asyncweb Issue Type: Improvement Components: Server Environment: AsyncWeb 0.9.0-CVS Reporter: Daniel Wirtz 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.

Assigned: (ASYNCWEB-13) No possibility to determine server socket in HttpService
United States	2008-04-30 09:39:55
[ https://issues.apache.org/jira/browse/ASYNCWEB-13?page=co m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Vermillard reassigned ASYNCWEB-13: ----------------------------------------- Assignee: Julien Vermillard > No possibility to determine server socket in HttpService > -------------------------------------------------------- > > Key: ASYNCWEB-13 > URL: htt ps://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 > > 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.

Updated: (ASYNCWEB-13) No possibility to determine server socket in HttpService
United States	2008-04-30 09:41:56
[ https://issues.apache.org/jira/browse/ASYNCWEB-13?page=co m.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: htt ps://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.

Commented: (ASYNCWEB-13) No possibility to determine server socket in HttpService
United States	2008-05-19 05:01:55
[ https:/ /issues.apache.org/jira/browse/ASYNCWEB-13?page=com.atlassia n.jira.plugin.system.issuetabpanels:comment-tabpanel&foc usedCommentId=12597909#action_12597909 ] Julien Vermillard commented on ASYNCWEB-13: ------------------------------------------- commited a fix in Asyncweb trunk server module. can you confirm it's ok for you ? > No possibility to determine server socket in HttpService > -------------------------------------------------------- > > Key: ASYNCWEB-13 > URL: htt ps://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.

Resolved: (ASYNCWEB-13) No possibility to determine server socket in HttpService
United States	2008-06-04 08:57:45
[ https://issues.apache.org/jira/browse/ASYNCWEB-13?page=co m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wirtz resolved ASYNCWEB-13. ---------------------------------- Resolution: Fixed > No possibility to determine server socket in HttpService > -------------------------------------------------------- > > Key: ASYNCWEB-13 > URL: htt ps://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.

Closed: (ASYNCWEB-13) No possibility to determine server socket in HttpService
United States	2008-06-04 09:01:45
[ https://issues.apache.org/jira/browse/ASYNCWEB-13?page=co m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Vermillard closed ASYNCWEB-13. ------------------------------------- closing > No possibility to determine server socket in HttpService > -------------------------------------------------------- > > Key: ASYNCWEB-13 > URL: htt ps://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.

[1-6]

about | contact Other archives ( Real Estate discussion Medical topics )