On Friday, February 22, 2013 8:14:51 AM UTC+1, Scott L. Burson wrote: > > On Thu, Feb 21, 2013 at 9:41 PM, petter <[email protected] <javascript:> > > wrote: > >> >> http://www-local:8080/pub/images/weblocks-alien-small.png I get the >> weblocks alien >> http://www-local:8080/pub/images/movie.mp4 I get a video player >> interface with black content which does not respond when I hit the play >> button >> http://techslides.com/demos/sample-videos/small.mp4 I get the same >> player interface with video content >> If I download small.mp4 and put it into the images directory and try >> http://www-local:8080/pub/images/small.mp4 I get a video player >> interface with black content which does not respond when I hit the play >> button >> > > Well, then, I return to my previous suggestion: use Wireshark to see > exactly what the browser is sending to the server. > > If you haven't used Wireshark before, this may take some study, but it's > an extremely useful tool that you would do well to have a little > familiarity with. >
I' more familiar with tcpdump, even though I'm not that familiar with the actual HTTP protocol. I could try to serve the same file with plain Hunchentoot and see if the results are the same... -- You received this message because you are subscribed to the Google Groups "weblocks" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/weblocks?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
