[Feature]: Include more http representation headers in site::Resource

[Tzal3x]

Description

Identify any useful headers that could be added to the site::Resource sui object's metadata.

So far only the Content-Encoding and Content-Type representation headers are included to the site::Resource object.

e.g.

"content_encoding":string"plaintext"
"content_type":string"text/css"

We should enrich this.

TBD: There is also the option to support any header, but that would make testing harder.

Component

portal

Code of Conduct

• [X] I agree to follow this project's Code of Conduct.

[Tzal3x]

We should start from representation headers.

Representation headers include:

• Content-Type ✅
• Content-Encoding ✅
• Content-Language - define the language of the content
• Content-Range - useful for chunked data, i.e. when a resource is split up and loaded partially.
• Repr-Digest
• Content-Location - indicates an alternate location for the returned data. The selection of the resource returned will depend on the Accept headers in the original GET request.
• Digest (deprecated)

[Tzal3x]

Our use case matches nicely with the agent-driven content negotiation.

Upon a client request (browser), the portal (agent) fetches all the resources from sui + walrus as usual.

Then, the portal could return a 300 Multiple Choices and let the browser choose the right content representation of the site as shown in the attached image:

The server in this case is the server-side portal that has already fetched the site resources.

[Tzal3x]

After having a short discussion we concluded that it would be best allowing any type of header under the site::Resource. This could be implemented with a verctor of tuples (key-value header pairs) in the walrus sites smart contract.