<commit_before># Inline Additional Media Type Structured Syntax Suffixes

Treat responses with Content-Type suffixed with +json and +xml as inline documents.

# Motivation

If you are trying out some GET HTTP requests in your browser against an API that uses vendor Content-Types that adhere to Structured Syntax Suffixes, then it is annoying to have them downloaded, instead of showing them inline.

# Disclaimer

I myself prefer vendor Content-Types, against the "profile" link. This browser extension just makes things a tad easier, not more "right".

# MIT License

# References

* <http://tools.ietf.org/html/draft-ietf-appsawg-media-type-suffix-regs-02>
* <http://tools.ietf.org/html/draft-wilde-profile-link-02>

# Installation
<commit_msg>Link RFCs<commit_after># Inline Additional Media Type Structured Syntax Suffixes

Treat responses with Content-Type suffixed with +json and +xml as inline documents.

# Motivation

If you are trying out some GET HTTP requests in your browser against an API that uses vendor Content-Types that adhere to Structured Syntax Suffixes, then it is annoying to have them downloaded, instead of showing them inline.

# Disclaimer

I myself prefer vendor Content-Types, against the "profile" link. This browser extension just makes things a tad easier, not more "right".

# MIT License

# References

* <http://tools.ietf.org/html/rfc6839>
* <http://tools.ietf.org/html/rfc6906>

# Installation

{'fraction_non_alphanumeric': 0.0718771807397069, 'fraction_numerical': 0.00837404047452896, 'mean_word_length': 4.57976653696498, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 2}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7331544', 'n_tokens_mistral': 415, 'n_tokens_neox': 394, 'n_words': 175}