Some Russian CDNs start blocking any request except static files

[zheka79739]

Some Russian CDNs start blocking any request except static files.
Example:
GET /somepath/example.mp4 - works fine
GET /somepath/example.mp4/45ba899f-ba04-4492-aa1a-e7714865ddb6 - blocked with 403 error
GET /somepath - blocked
GET /somepath/45ba899f-ba04-4492-aa1a-e7714865ddb6 - blocked
GET /somepath/example.mp4/?someparam=somevalue - blocked

Any ideas how to bypass this restrictions?

[RPRX]

伪装成 MP4 然后 GET /somepath/45ba899f-ba04-4492-aa1a-e7714865ddb6.mp4

[zheka79739]

How to make it in xhttp configuration? There is only path option and it doesn't allow to add a file extension to the end of request.

[26X23]

How to make it in xhttp configuration? There is only path option and it doesn't allow to add a file extension to the end of request.

Add extension to the path and try to move session id and sequence id from path to headers with "sessionIDPlacement": "header", "sessionIDKey": "something", "seqPlacement": "header", "seqKey": "seqkey" configuration options.

[zheka79739]

Not working. Any request with trailing / is blocked.
somepath/somefile.mp3 - not blocked
somepath/somefile.mp3/ - blocked
Now the problem is both x-ray and vpn apps always adds a trailing / to the end of a request.

[lenow55]

Hi, also face with this issue. I need to be able to remove a trailing / from the path to penetrate CDN.

[Tangent-90C]

I don’t understand. Request paths like /somepath/example.mp4 are encrypted and invisible—how can it block traffic based on them?

[Tangent-90C]

I don’t understand. Request paths like /somepath/example.mp4 are encrypted and invisible—how can it block traffic based on them?

Oh, is CDN