Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

chrox
Copy link
Contributor

@chrox chrox commented Oct 15, 2024

This should close #11371.

@chrox chrox requested a review from a team as a code owner October 15, 2024 18:15
@chrox chrox changed the title fix(core): expose content-range header in asset protocol fix(core): expose content-range header in asset protocol, closes #11371 Oct 15, 2024
Copy link
Contributor

github-actions bot commented Oct 15, 2024

Package Changes Through 1a0017b

There are 2 changes which include tauri with patch, @tauri-apps/api with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package current next
@tauri-apps/api 2.0.2 2.0.3
tauri 2.0.4 2.0.5

Add another change file through the GitHub UI by following this link.


Read about change files or the docs at github.com/jbolda/covector

@chrox chrox force-pushed the expose-content-range-header branch from 54dee78 to 1a0017b Compare October 15, 2024 18:55
@amrbashir amrbashir requested a review from tweidinger October 15, 2024 22:53
Copy link
Contributor

@tweidinger tweidinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be fine to expose this header since we should have no cors restrictions.

@lucasfernog lucasfernog merged commit e1bf6ef into tauri-apps:dev Oct 17, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[bug] fetch and XHR response has no content-range header
3 participants