I believe it'd be application/jose per https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-31#section-9.2.1 and https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-31#section-4.1.9 and one could further distinguish between JWS/JWE using the alg header or the number of periods in the compact serialization.
On Wed, Sep 10, 2014 at 5:37 AM, Sergey Beryozkin <[email protected]> wrote: > Hi All, > > What would be the right HTTP Content-Type value to identify a given > compact JWE or JWS serialization payload transmitted as an HTTP message > payload (as opposed to as a header or query value). > I see both JWE and JWS compact serializations can use a 'cty' header > property to identify the encrypted or signed content but it is not clear > how the actual JWE/JWS compact serializations are identified. > > Something like > > application/jose+jws;format=compact > application/jose+jwe;format=compact > > with a format parameter being optional, > > or somehow else ? > > Sorry if I missed something, > > Thanks, Sergey > > _______________________________________________ > jose mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/jose >
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
