fix(core): expose content-range header in asset protocol (#11374)

chrox · web-flow · commit e1bf6ef8cbe3 · 2024-10-17T08:41:27.000-03:00
diff --git a/.changes/asset-protocol-expose-content-range.md b/.changes/asset-protocol-expose-content-range.md
@@ -0,0 +1,5 @@
+---
+"tauri": patch:bug
+---
+
+Expose `content-range` header in `range` response of `asset` protocol
diff --git a/crates/tauri/src/protocol/asset.rs b/crates/tauri/src/protocol/asset.rs
@@ -86,6 +86,7 @@ fn get_response(
     .and_then(|r| r.to_str().map(|r| r.to_string()).ok())
   {
     resp = resp.header(ACCEPT_RANGES, "bytes");
+    resp = resp.header(ACCESS_CONTROL_EXPOSE_HEADERS, "content-range");
 
     let not_satisfiable = || {
       Response::builder()

-Original file line number
+Diff line change
@@ @@ -0,0 +1,5 @@ @@
 +---
 +"tauri": patch:bug
 +---
++
 +Expose `content-range` header in `range` response of `asset` protocol
Original file line number	Diff line number	Diff line change
`@@ -86,6 +86,7 @@ fn get_response(`
`86`	`86`	`.and_then(\|r\| r.to_str().map(\|r\| r.to_string()).ok())`
`87`	`87`	`{`
`88`	`88`	`resp = resp.header(ACCEPT_RANGES, "bytes");`
	`89`	`+ resp = resp.header(ACCESS_CONTROL_EXPOSE_HEADERS, "content-range");`
`89`	`90`
`90`	`91`	`let not_satisfiable = \|\| {`
`91`	`92`	`Response::builder()`