Re: HTTP Request's Content Encoding field

m: Jmeter Tea > Sent: 25 December 2018 20:22 > To: JMeter Users List > Subject: Re: HTTP Request's Content Encoding field > > Thank you for answering my question, > But still, what is the usage of setting a valid value, What is the benefit > over setting Content-Type

RE: HTTP Request's Content Encoding field

From: Jmeter Tea Sent: 25 December 2018 20:22 To: JMeter Users List Subject: Re: HTTP Request's Content Encoding field Thank you for answering my question, But still, what is the usage of setting a valid value, What is the benefit over setting Content-Type header parameter? On Tue, Dec 25, 201

Re: HTTP Request's Content Encoding field

Thank you for answering my question, But still, what is the usage of setting a valid value, What is the benefit over setting Content-Type header parameter? On Tue, Dec 25, 2018 at 3:59 PM glin...@live.com wrote: > It is being used at least: > > 1. For setting request header > < > https://githu

Re: HTTP Request's Content Encoding field

It is being used at least: 1. For setting request header 2. For encoding POST request data

Re: HTTP Request's Content Encoding field

glinius: I get the same results as leave empty or UTF-16 (as GET http://www.google.com/?漢字), also I want a use case when you *need *it On Wed, Sep 26, 2018 at 8:23 AM, glin...@live.com wrote: > Try sending a HTTP GET request with a Chinese character and encoding set to > US-ASCII. > > > > -- >

Re: HTTP Request's Content Encoding field

Try sending a HTTP GET request with a Chinese character and encoding set to US-ASCII. -- Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additi