Infrastructure/logto
0
Fork 0
mirror of https://github.com/logto-io/logto.git synced 2024-12-16 20:26:19 -05:00
Code Issues Activity

chore: split and add dedicated changeset for tunnel (#6632)

Browse source
This commit is contained in:
Charles Zhao 2024-09-26 10:55:04 +08:00 committed by GitHub
parent f5b17f31f1
commit 349a6a405b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 9 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
.changeset/tasty-kings-fetch.md
View file

@ -1,9 +1,8 @@
--- ---
"@logto/phrases": patch "@logto/phrases": patch
"@logto/tunnel": patch
"@logto/core": patch "@logto/core": patch
--- ---
fix an issue that prevent mp4 video from playing on Safari fix an issue that prevent mp4 video from playing in custom sign-in pages on Safari browser
Safari browser uses range request to fetch video data, but it was not supported by the `@logto/tunnel` CLI tool and `koa-serve-custom-ui-assets` middleware in core. This prevents our users who want to build custom sign-in pages with video background. In order to fix this, we need to partially read the video file stream based on the `range` request header, and set proper response headers and status code (206). Safari browser uses range request to fetch video data, but it was not supported by the `koa-serve-custom-ui-assets` middleware in core. This prevents our users who want to build custom sign-in pages with video background. In order to fix this, we need to partially read the video file stream based on the `range` request header, and set proper response headers and status code (206).

7
.changeset/violet-ligers-carry.md Normal file
View file

@ -0,0 +1,7 @@
---
"@logto/tunnel": patch
---
support range request for mp4 video source hosting
Safari browser uses range request to fetch video data, but it was not supported by the `@logto/tunnel` CLI tool. This prevents our users who want to build custom sign-in pages with video background. In order to fix this, we need to partially read the video file stream based on the `range` request header, and set proper response headers and status code (206).