HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
byte serving does work in domino for attachments, BUT you have to deselect the compress option when attaching the file. This has been there since R5.
Carl Tyler Epilio
I also did a screen recording showing the problemactic code 200 requests.
https://www.siriusonline.de/WebHosting/videotest/2021-05-03%2010-24-23%20Domino%20Range%20Requests%20not%20working.mp4
What do you see in the code 206 results you get for the request header variable "range"?
(You can see this if you click on a request in the developer console on the right hand side under "Request headers")
Like I said it is depending on the syntax of the range request header variable (which is controlled by the browser):
working ---> Range: bytes=33259520-
not working ---> Range: bytes=47153152-183861338
Mark Reiser
sirius-net GmbH
Byte serving still works at least since R5 i suppose til today.
See attached gif in my last post with status codes 206 while going back and forward in a sample video.
Byte serving has been a long time limitation in domino attachments since...R5 I suppose. Long time missed...
"Just open in Chrome browser, open developer console (F12) and watch requests while spooling within the video."
See attached gif.
Thanks for clarification, missed too many of these informations in original post.
Anyway I just tested with two browsers with your sample video and I always got 206 codes while spooling back and forward and multiple small transfers between 50...800k. So it seems working for me.
Maybe this is a proxy, firewall or cache thing?
>>Domino automatically uses byte-range serving if the Web client uses a product that supports this feature. No configuration is necessary. "
Unfortunately this is not the case!
If the client sends a range request with the following header variable, Domino sends out the whole file instead of the requested chunk only. This is a typical case when spooling in a HTML5 video with a Chrome browser.
Range: bytes=47153152-183861338
Instead of sending a 206 it sends a 200 return code.
If the range request comes as follows Domino is capable of delivering the request correctly.
Range: bytes=33259520-
>>Note: Compressed files cannot be downloaded using Domino byte-range serving.
This is correct. However we are attemting it on video files residing withing the domino\html folder.
We therefore made a tiny example page for reproducing the problem:
https://www.siriusonline.de/WebHosting/videotest/index.html
Just open in Chrome browser, open developer console (F12) and watch requests while spooling within the video.
Mark Reiser
sirius-net GmbH
"Domino automatically uses byte-range serving if the Web client uses a product that supports this feature. No configuration is necessary. "
Note: Compressed files cannot be downloaded using Domino byte-range serving.
Source: http://www.redbooks.ibm.com/redpapers/pdfs/redp4182.pdf