https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #15 from Konstantin Kolinko ---
One of widely used technologies of using plaintext vs encrypted communication
over the same connection is STARTTLS.
https://en.wikipedia.org/wiki/STARTTLS
It has known weaknesses and I would not rec
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #14 from romain.manni-bucau ---
Ok, then close the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #13 from Remy Maucherat ---
An extend capability is useless as well. There is no guarantee the connectors
design or API will remain stable, so it is just as simple to make whetever
necessary changes to Tomcat as part of the build pr
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #12 from romain.manni-bucau ---
@Mark: there is a discussion - think it is on the list - to make connectors
easier to impl/extend. For me it should be as easy as wrapping HTTP and HTTPs
connectors - = implementing it as a wrapper of
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #11 from Mark Thomas ---
I remain unconvinced that this feature is a) necessary or b) a good idea.
(In reply to romain.manni-bucau from comment #10)
> Why Tomcat couldn't get this? The code itself is very limited.
Implementing thi
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #10 from romain.manni-bucau ---
> I think you are introducing a semantic difference where there is none: a web
> service and a web application are the same thing. The fact that a browser is
> one kind of client is irrelevant.
On
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #9 from Christopher Schultz ---
(In reply to romain.manni-bucau from comment #8)
> A webservice doesnt have all the "browser" constraints and defaults (where
> all comments are right).
I think you are introducing a semantic differe
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #8 from romain.manni-bucau ---
A webservice doesnt have all the "browser" constraints and defaults (where all
comments are right).
I used few providers where you were not able to bind any other port than one in
a reliable manner -
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #7 from Christopher Schultz ---
(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
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #6 from romain.manni-bucau ---
The "not that hard" is really dependent on your environment. 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 we
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #5 from Christopher Schultz ---
This is somewhat related to the long-standing request (can't find the
enhancement in BZ at the moment) to emit a plain-text error message from a TLS
connector that is contacted by a non-TLS client. Th
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #4 from romain.manni-bucau ---
@Mark: doesnt change the fact you still have a single port to bind and can need
both (internal vs external for a trivial sample). Also several cloud providers
are exposing tomcat directly whatever you
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #3 from Mark Thomas ---
Given that user agents are written on the basis of different default ports for
HTTP and HTTP I don't see this causing anything but problems for end users.
Regarding cloud providers I'd be surprised if any we
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #2 from romain.manni-bucau ---
Here is the interest then ;)
In embedded mode it would be very fancy, in particularly since embedded tomcat
supports a single port and also cause cloud providers allows most of the time a
single port
https://bz.apache.org/bugzilla/show_bug.cgi?id=58551
--- Comment #1 from Remy Maucherat ---
There has never been any interest in Tomcat to add "port unification", and now
that unencrypted is going to be on the decline, it is even less likely this
feature would be accepted.
--
You are receiving
16 matches
Mail list logo
