On 29/03/2016 04:35, Amey Rokde wrote:
> Christoph
>
> Fair enough that it is not a security leak . Can you throw some light on
> what's happening internally so as to understand why we get this garbled
> data to be downloaded.
What you are seeing are the opening bytes of the TLS handshake. The
cl
Christoph
Fair enough that it is not a security leak . Can you throw some light on
what's happening internally so as to understand why we get this garbled
data to be downloaded.
sorry for pushing
Amey
On Mon, Mar 28, 2016 at 10:00 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
>
Amey,
On 3/28/16 11:25 AM, Amey Rokde wrote:
> May be i didn't explained my question properly. What we have is a single
> web application running on https port 7070. This port is configured for
> https connection only and that the reason there is single connector. What
> we are seeing is if by mis
Hi Christoph
May be i didn't explained my question properly. What we have is a single
web application running on https port 7070. This port is configured for
https connection only and that the reason there is single connector. What
we are seeing is if by mistake
or intentionally the user types ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amey,
On 3/28/16 3:54 AM, Amey Rokde wrote:
> Dear Community
>
> We are using the apache-tomcat-7.0.55 and have configured only one
> SSL connector (7070).
>
> The SSL connection (https) )works properly and i am able to fetch
> the request. But if w
Dear Community
We are using the apache-tomcat-7.0.55 and have configured only one SSL
connector (7070).
The SSL connection (https) )works properly and i am able to fetch the
request. But if we make http request we get the garbled data to be
downloaded in the browser.
I tried searching over the n
