Accept-Ranges skipped by Dispatcher

[arvindpandey]

Hi Team,

To play video in Safari browser, we understood that "Accept-Ranges" header in response is required.

However, when we access our site and check response header, we dont find this specific header.  However, if we simply access site using publish instances IP, we can see this header in response and as a result, Video being played well in Safari.

We tried to add this header in Clientheader.any file, but no luck.

Do you have any idea/Have you ever faced similar issue?

[arunpatidar]

Hi @arvindpandey 
You need below response headers,

Accept-Ranges: bytes

Content-Range: bytes 0-5455072/5455073

we has the similar issue when access video via CDN, and fix was to Disable sending to Origin header "Accept-encoding"

[arvindpandey]

Hi @arunpatidar ,

Thanks a lot for your kind reply.

As per our understanding Accept-ranges and content-range are automatically enabled in Apache 2.X.

However, we manually added below lines in Dispatcher:

Header set Accept-Ranges bytes
Header set Content-Range 'bytes 0-5455072/5455073'

Now in response header, we see Content-Range but Accept-Ranges is still missing.

Also, in our case we dont have CDN but a firewall- Radware.

So flow is Browser- Radware-Balancer-Dispacther-Publish.

When you say "Disable sending to Origin header "Accept-encoding" , what does it mean ..what action we should take in our case?

Any pointer will be really appreciated.

[arunpatidar · Accepted solution]

we have stop sending the Accept-encoding header for mp4 file from AKMAIA to Dispatcher.

Our AKAMAI team was not sure about the issue so they tried following

• Disable sending to Origin header "Accept-encoding" to dispatcher
• Disable caching in Akamai (only browser and origin)

but finally they found out only first one will work