Support a relative URL of a resource in a bundle. #647

hayatoito · 2021-04-08T05:00:23Z

It might be worth considering to support a relative URL in the bundle format.

I've heard this feature request from several people. I've searched an existing issue, but I couldn't find one so let me file an issue.

Use cases:

Regarding subresource loading use case, we use the following syntax in the main doc:

<link rel=webundle href=https://example.com/app/bundle.wbn resources=".....">

Because we have path restriction, the resources in the bundle must start with https://example.com/app/, such as:

It seems a bit redundant. If we support a relative URL, each subresource doesn't have to include a redundant common prefix, and can be:

./top.js
./util1.js
./util2.js
...

We have to decide on which base a relative URL should be resolved. For subresource loading use cases, it's clear.
For other use cases, TBD.

The other benefits are:

A bundle can be more portable. For example, we can move bundle.wbn from https://example.com/app/ to https://example.com/other/, freely, without re-creating a bundle.
The size of a bundle can be reduced.

The text was updated successfully, but these errors were encountered:

hayatoito · 2021-04-08T05:13:44Z

#617 can be related. We need to make primary URL optional.

jyasskin · 2021-04-08T17:27:58Z

Yep, I think we do this by either

putting the base URL in a section (possibly one holding a map of several metadata values), or
using the bundle's URL as the base.

This CL changes WebBundleParser to support relative URLs in the index section. And uses the web bundle's URL as the base URL for SubresourceWebBundles feature. Bug: 1247939, WICG/webpackage#647 Change-Id: Ie41125c293791d9209f94e59e5c9c8af3ac9778f

This CL changes WebBundleParser to support relative URLs in the primary URL, manifest and index section. And uses the web bundle's URL as the base URL for SubresourceWebBundles feature. Bug: 1247939, WICG/webpackage#647 Change-Id: Ie41125c293791d9209f94e59e5c9c8af3ac9778f

horo-t · 2021-09-10T12:14:38Z

Hi.

I created a PR to support the second idea "using the bundle's URL as the base." in @jyasskin 's comment in subresource bundle.

I think we can introduce a base section which can override the base URL in future. But even so, I think it is reasonable to use the bundle's URL as the base URL which can be overridden by the base section.

This CL changes WebBundleParser to support relative URLs in the primary URL, manifest and index section. And uses the web bundle's URL as the base URL for SubresourceWebBundles feature. Bug: 1247939, WICG/webpackage#647 Change-Id: Ie41125c293791d9209f94e59e5c9c8af3ac9778f

hayatoito · 2021-09-13T03:38:08Z

Thanks!
Yes, I think we can agree on the "using the bundle's URL as the base".
While I can appreciate the PR, we probably want to wait for a resolution of wpack-wg/bundled-responses#14.

This CL changes WebBundleParser to support relative URLs in the primary URL, manifest and index section. And uses the web bundle's URL as the base URL for SubresourceWebBundles feature. Bug: 1247939, WICG/webpackage#647 Change-Id: Ie41125c293791d9209f94e59e5c9c8af3ac9778f

This CL changes WebBundleParser to support relative URLs in the primary URL, manifest and index section. And uses the web bundle's URL as the base URL for SubresourceWebBundles feature. Bug: 1247939, WICG/webpackage#647 Change-Id: Ie41125c293791d9209f94e59e5c9c8af3ac9778f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3150318 Reviewed-by: Hayato Ito <hayato@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/main@{#924647}

…ubresourceWebBundles feature, a=testonly Automatic update from web-platform-tests Support relative URL in Web Bundle for SubresourceWebBundles feature This CL changes WebBundleParser to support relative URLs in the primary URL, manifest and index section. And uses the web bundle's URL as the base URL for SubresourceWebBundles feature. Bug: 1247939, WICG/webpackage#647 Change-Id: Ie41125c293791d9209f94e59e5c9c8af3ac9778f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3150318 Reviewed-by: Hayato Ito <hayato@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/main@{#924647} -- wpt-commits: 68c75f6da95e3da84c83eb4930ba5a5c2341637a wpt-pr: 30416

hayatoito · 2021-11-11T05:17:36Z

Fixed. Now we support a relative URL.

This CL changes WebBundleParser to support relative URLs in the primary URL, manifest and index section. And uses the web bundle's URL as the base URL for SubresourceWebBundles feature. Bug: 1247939, WICG/webpackage#647 Change-Id: Ie41125c293791d9209f94e59e5c9c8af3ac9778f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3150318 Reviewed-by: Hayato Ito <hayato@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/main@{#924647}

This CL changes WebBundleParser to support relative URLs in the primary URL, manifest and index section. And uses the web bundle's URL as the base URL for SubresourceWebBundles feature. Bug: 1247939, WICG/webpackage#647 Change-Id: Ie41125c293791d9209f94e59e5c9c8af3ac9778f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3150318 Reviewed-by: Hayato Ito <hayato@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/main@{#924647} NOKEYCHECK=True GitOrigin-RevId: 17698fb7dfb32500eaa631a821082128a2f3faa7

hayatoito added the subresource-loading label Apr 8, 2021

hayatoito mentioned this issue Apr 9, 2021

[Meta] A long term plan for subresource loading #648

Open

19 tasks

chromium-wpt-export-bot mentioned this issue Sep 9, 2021

Support relative URL in Web Bundle for SubresourceWebBundles feature web-platform-tests/wpt#30416

Merged

hayatoito mentioned this issue Sep 9, 2021

Needs Clarification: A relative URL is supposed to work in index section? wpack-wg/bundled-responses#14

Closed

horo-t mentioned this issue Sep 10, 2021

Support relative URLs in bundle in subresource loading #678

Merged

hayatoito closed this as completed Nov 11, 2021

irori mentioned this issue Apr 28, 2022

Improve relative URLs support in Go/JavaScript bundle tools #739

Closed

KenjiBaheux mentioned this issue Dec 16, 2022

TAG feedback w3c/miniapp-packaging#64

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Support a relative URL of a resource in a bundle. #647

Support a relative URL of a resource in a bundle. #647

hayatoito commented Apr 8, 2021 •

edited

Loading

hayatoito commented Apr 8, 2021 •

edited

Loading

jyasskin commented Apr 8, 2021

horo-t commented Sep 10, 2021

hayatoito commented Sep 13, 2021 •

edited

Loading

hayatoito commented Nov 11, 2021

Support a relative URL of a resource in a bundle. #647

Support a relative URL of a resource in a bundle. #647

Comments

hayatoito commented Apr 8, 2021 • edited Loading

hayatoito commented Apr 8, 2021 • edited Loading

jyasskin commented Apr 8, 2021

horo-t commented Sep 10, 2021

hayatoito commented Sep 13, 2021 • edited Loading

hayatoito commented Nov 11, 2021

hayatoito commented Apr 8, 2021 •

edited

Loading

hayatoito commented Apr 8, 2021 •

edited

Loading

hayatoito commented Sep 13, 2021 •

edited

Loading