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.
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,
I was wrong. It is working after I added the useHttpOnly=false to the
context.
Thanks a lot for the help.
Al.
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 Windows
Media Player cannot play the file. The player might not
support the file type or might not
Hi Chuck,
Here are the two headers and the mime part are both the same:
tomcat 6
Server Apache-Coyote/1.1
Pragma No-cache
Cache-Control no-cache
Expires Wed, 31 Dec 1969 16:00:00 PST
Accept-Ranges bytes
Etag W/42566016-119615262
Last-Modified Tue, 27 Nov 2007 08:37:00 GMT
Content-Type
From: al pl [mailto:uhotsp...@gmail.com]
Subject: Re: Problem with wmv file in tomcat 7
Browser?
tomcat 6
Pragma No-cache
Cache-Control no-cache
tomcat 7
Cache-Control private
Note the caching control differences. You might want to check the headers a
few more times to see
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
2011/11/19 al pl uhotsp...@gmail.com:
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
