Allow Set for ContentType property of Parameter

[pboisso]

Is your feature request related to a problem? Please describe.
I can't find a way to not write Content-Type for multipart form-data post. Migrating from v106.

Describe the solution you'd like
Could allow public Set to the ContentType property of the Parameter class?

Additional context
Please check difference between v106.15.0 on the left and v110.2.0 on the right.

[alexeyzimarev]

It's a usage question, please do not ignore the contribution guidelines when opening issues.

As for the question itself, you can create an instance of BodyParameter and specify the content type in the constructor call. The add it using AddParameter.

[pboisso]

Hi @alexeyzimarev,

Thanks for the answer. However, I feel this is still a feature request.

Trying to add BodyParameter the way you described, but when I do, the parameters do not even appear in the request. There is no body in that request, only Post parameters.

                request.AddParameter(new BodyParameter(s.Key, s.Value, null) { Type = ParameterType.GetOrPost });

Does NOT work.

                request.AddParameter(s.Key, s.Value, ParameterType.GetOrPost);

Does work, but by adding Content-Type and charset.

I've tried several ways, but I could not find a way to just add a plan Post parameter without Content-Type/charset being added.

Note that

                request.AddParameter(s.Key, s.Value);

Was working fine in v106 without any other settings being changed.

Could you consider adding ContentType in the AddParameter method?

Thanks.

Patrice

[alexeyzimarev]

Of course it doesn't work as you override the parameter type.

[pboisso]

@alexeyzimarev,

Here is the code in v106:

var client = new RestSharp.RestClient();
client.BaseUrl = strUrlToCall;
var request = new RestSharp.RestRequest(RestSharp.Method.POST);
request.AlwaysMultipartFormData = true;
request.AddParameter("name", strFrom);
request.AddParameter("email", strEmail);
request.AddParameter("body", strHTMLBody);
var response = client.Execute(request);

The following code in v110:

var client = new RestClient();
var request = new RestRequest(urlToCall, Method.Post);
request.AlwaysMultipartFormData = true;
request.AddParameter("name", strFrom);
request.AddParameter("email", strEmail);
request.AddParameter("body", strHTMLBody);
var response = client.Execute(request);

does NOT give the same post. Content-type is added for each parameter (as displayed in the image in the first post of this thread).

If I use

request.AddParameter(new BodyParameter("name", strFrom));
request.AddParameter(new BodyParameter("email", strEmail));
request.AddParameter(new BodyParameter("body", strHTMLBody));

as you suggested, I get a "Invalid content type string" error message.

Please advise how to run the v106 code above in v110 so that I get the same exact post output.

Thanks from a simple developer just trying to migrate to latest version.

Patrice

[alexeyzimarev]

Ok, that should've been there from the beginning. It's hard to understand what your goal is when there's no code.

So, basically, you don't want to set the content type, you want to remove it. RestSharp doesn't explicitly add content type to multipart-form request body parameters. It's the default message handler from .NET who does that.

Here's the StringContent constructor, which always sets the content type:

        public StringContent(string content, Encoding? encoding, string? mediaType)
            : base(GetContentByteArray(content, encoding))
        {
            // Initialize the 'Content-Type' header with information provided by parameters.
            MediaTypeHeaderValue headerValue = new MediaTypeHeaderValue((mediaType == null) ? DefaultMediaType : mediaType);
            headerValue.CharSet = (encoding == null) ? HttpContent.DefaultStringEncoding.WebName : encoding.WebName;

            Headers.ContentType = headerValue;
        }

[pboisso]

Hello @alexeyzimarev,

Thanks for re-opening and the consideration. I use RestSharp to post a form to a ticket service. For some reason, if the content type is set for post parameters, they handle the message differently.

Also note that I'm also talking about the post parameter content-type here, not the message content-type, which is still properly set to multipart/form-data

So the fact content-type and charset is also added for each parameter does something different to the receiving party. That's the only difference between v106 and v110 (from raw output from Charles).

I've also tried the DisableCharset option, but that does not change the behavior. I've tried with different charset also (utf-8 and ISO-8859-1), but with no luck.

At the end, I don't know if it's a charset or content-type issue, or both, but the only difference between v106 and v110 raw http output is the line "Content-Type: text/plain; charset=utf-8" which is printed for each POST parameter in the form, right after the form boundary line.

I hope this help.

Thanks,
Patrice

[alexeyzimarev]

That's basically what I described in my previous comment. It's the default behaviour of StringContent.

[alexeyzimarev]

So even if you set the content type for the parameter to null, the StringContent constructor will override it with DefaultMediaType, which is text/plain, and that's what you see.

[pboisso]

Not familiar with the internals, that's the goal of using a library ;) Just reporting that http raw output has changed from v106 to v110 with the same code and did not find a way to update the code to make the output the same. Unfortunately, that has apparently some impact on the receiving end. Reverting back to v106 for now. Thanks for the help.

[alexeyzimarev]

Well, the point of FOSS is to have collaboration, so the issues can be resolved by the community.

I can confirm that the content type header for individual parameters can be removed after the content object is created. Not sure what the API should look like. My current thought is that it should be a new, separate parameter type like MultipartDataFormParameter. Adding such parameters would automatically ensure the form is set with the correct type and content type, as well as the parameter class would allow to override the parameter content type, including setting it to null.

I want to make clear that although the behaviour of RestSharp has changed on the transport level, it didn't become incorrect. Setting the content disposition header for multipart-data form parameters is the correct behaviour.

[Frankwayne]

I'm running into this issue as well trying to connect to a java service. While RestSharp is behaving correctly, I can't control external servers.

[Frankwayne]

MultipartDataFormParameter

Sounds good to me, idk if you will want to handle changing the behavior of StringContent inside of the constructor or with a method that will remove the ContentType.

I could be wrong as I haven't had the time to really review the RFC but if you are adding in the ability to write invalid transport text, then I would support a method to remove the ContentType of the multimedia part.