[
http://jira.jboss.com/jira/browse/JBESB-807?page=comments#action_12384322 ]
Tom Fennelly commented on JBESB-807:
------------------------------------
At this stage in the game I'd be inclined to move away from JBossRemoting for HTTP
support. I've played with Jetty and it seems like a far more flexible option for us.
It allows us have far more control over the HTTP request and response, as well as security
related issues (re this issue).
JBossRemotingGateway doesn't support Http BASIC Auth (and
probably more)
------------------------------------------------------------------------
Key: JBESB-807
URL:
http://jira.jboss.com/jira/browse/JBESB-807
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 3
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
Fix For: 4.2.1
Talked with Ron Sigal and he thinks we might have to explicitly use the Servlet transport
(i.e. the CoyoteInvoker might not be configurable for BASIC auth).
Here's what Ron said exactly.....
"1. HTTPServerInvoker is obsolete. It's been replaced by CoyoteInvoker.
2. According to my O'Reilly Tomcat book, BASIC authorization is configured in the
web.xml file by the <login-config> element. But CoyoteInvoker doesn't use the
full Tomcat implementation, just the Coyote adapter. I'm really not sure if the
Coyote adapter has anything to do with the web.xml file.
3. There is another Remoting transport, the servlet transport, which really does use
Tomcat. It uses a servlet as a front end to the server invoker. There's even a
web.xml file: src\etc\web\web.xml in the Remoting project directory."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira