https://bz.apache.org/bugzilla/show_bug.cgi?id=58551

--- Comment #7 from Christopher Schultz <ch...@christopherschultz.net> ---
(In reply to romain.manni-bucau from comment #6)
> The "not that hard" is really dependent on your environment.

Fair enough, but you mentioned embedded environment: very easy to add another
connector programmatically.

> Not being in
> the spec is one thing and you seem to keep speaking of web applications
> where the most common use case for such a feature is webservices

What's the difference between a "web application" and a "webservice"?

> IMO (allowing "internal" not secured communication and "external"
> secured communications)

I understand, and I operate such an environment. I also happen to operate in a
"cloud" environment where I have never had any problems connecting things
together, whether using HTTP or HTTPS.

> I wouldn't activate it by default as well but I would add a flag on the
> connector to be able to do so (acceptPlain=true on a SSL connector for
> instance).

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to