NameValueCollection into equivalent javascript

Question

I have a c# code that uses NameValueCollection, and then webclient to send a post request to API.

I need to use an equivalent request but using javascript instead of c#, I tried the following:

$.ajax({
            type: "POST",
            url:  "https://api.pushover.net/1/messages.json",
            contentType: "application/json; charset=utf-8",
            dataType: "json",
            data: {
                "message": "xyz",
                "token": "xyz",
                "user": "xyz",
            },
            success: function(data) {
                console.log("push sent!");
            }
        });

But I get a 400 error, stating "bad request".

Please ignore the security perspective as the token & user are available to the user.

c# code is:

var parameters = new NameValueCollection {
            { "token", "xyz" },
            { "user", "xyz" },
            { "message", "xyz" }
        };

    using (var client = new WebClient())
    {
        client.UploadValues("https://api.pushover.net/1/messages.json", parameters);
    }

You say you tried something but it didn't work. What did you try? — Matt Ellen, May 24 '19 at 15:15
Hi @MattEllen, I tried something like below: `$.ajax({ type: "POST", url: "https://api.pushover.net/1/messages.json", contentType: "application/json; charset=utf-8", dataType: "json", data: { "message": "xyz", "token": "xyz", "user": "xyz", }, success: function(data) { console.log("push sent!"); } });` — Hatem Husam, May 24 '19 at 21:59
Did you get some kind of error? What behaviour did you expect? — Matt Ellen, May 24 '19 at 22:20
Yes @MattEllen, I got error "400 bad requests" when I tried to use the javascript code, on the other hand, c# code is working fine. — Hatem Husam, May 24 '19 at 22:30

score 0 · Answer 1 · answered May 25 '19 at 22:54

I'm not at my machine right now so I can't test this, but I would guess that you're not setting the content type in the Header property of the webclient in c#, so that is defaulting to application/x-www-form-urlencoded but in javascript you're setting the content type to application/json. If the server is not set up to accept that type then you'll get a 400 error.

Christian Gollhardt · Answer 2 · 2019-05-25T23:42:57.127

0

It's probably because of the trailing comma in "user": "xyz",. A trailing comma is disallowed in json while perfect valid in c#.

I tested it using Postman (I can highly recommend, when working with APIs).

With a comma we get simple 400 - Bad request:

Without a comma, we get at least an invalid token:

edited May 25 '19 at 23:42

answered May 25 '19 at 23:24

Christian Gollhardt

16,510
17
74
111

NameValueCollection into equivalent javascript

2 Answers2