Bill Barker wrote:
Before I start performing major surgery on the TC4/5 connector, I wanted toI don't remember the reason. I probably chose not to delegate since there might not have been any attributes ariginally in the Coyote Request object.
check on what is the reason for having the attributes field in CoyoteRequest
(instead of just delegating to the o.a.c.Request like the 3.3 Adapter does).
At the moment, the SSL request attributes are set on the o.a.c.Request
(because that's all that the Action knows about). This is Ok for
getAttribute, since it delegates when not found. But for getAttributeNames,
it only uses the names known to the attributes field (so no SSL attributes).
My strong preference is to delegate always (cleaner, esp. for TC 5 that will
be able to access Coyote directly). But I can fix this particular bug
either way.
So it wasn't done because it wasn't there; I don't think there ever was a Good Reason (TM) for that.
+1 to fix it.
What's the surgery you want to do ?
Remy
--
To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
