Konstantin,
I was wrong. It is working after I added the useHttpOnly="false" to the
context.
Thanks a lot for the help.
Al.
Another thing I realized is that the whole wmv file is sent to the browser
per it's request. So why doesn't it hand off the file to windows media
player and why does windows media player requests the file again?
Thanks,
Al
Konstantin,
*
*
*Thanks for the info. I believe it is related to that HttpOnly flag as you
said because in access log it shows that in response to fetching the video
file it sends the same amount of bytes as my login screen. I set the
useHttpOnly flag to false in app context but that didn't help. H
Chuck,
Regarding the browser it happens in both Chrome and IE and I don't think it
is browser related.
And regarding the cache header directives since that page is coming from a
secured location per
http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html I changed the
Form Authenticator valve so
Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: al pl [mailto:uhotsp...@gmail.com]
> > Subject: Problem with wmv file in tomcat 7
>
> > since I have upgraded the tomcat to version 7.0.22, the
> > same windows media player gives an error saying "
Hi,
I have bunch of .wmv files which used to work fine in tomcat 6 when the
user clicked on the link. The windows media player used to start buffering
and then playing them, but since I have upgraded the tomcat to version
7.0.22, the same windows media player gives an error saying "Windows Media
P
