Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Support of setting "Content-*" headers in transaction tags #67

Open
hatskier opened this issue Apr 15, 2021 · 1 comment
Open

Support of setting "Content-*" headers in transaction tags #67

hatskier opened this issue Apr 15, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@hatskier
Copy link

Currently, it's possible to set the "Content-Type" tag as the transaction data content type. It's used as an HTTP header when the transaction data is rendered in a browser.

It would be nice to enable support for all other "Content-*" headers (esp. "Content-Encoding"). It will be very useful because senders will be able to compress their data with gzip and set "Content-Encoding: gzip". This way the browsers will automatically decompress tx data using gzip algorithm while rendering the tx data. This approach may help to save more than 50% on tx rewards.

@TheLoneRonin TheLoneRonin added the enhancement New feature or request label Apr 18, 2021
@webjunkie
Copy link

Was this ever approached? For me it seems to still not be supported.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants