Home/ Questions/Q 652561
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T22:17:09+00:00

Which is the best way (in performance and security) to send multiple parameters to

  • 0

Which is the best way (in performance and security) to send multiple parameters to a web page (on a different server), considering that the length of the parameters may vary because I’m sending a list of products, and the customer may have selected more than one product, so we need to send each product on the querystring to the other page.

For example (I’m on C#); I want to call a web page like this:

  • Simple Querystring: thepage.asp?Product=1&Name=Coffee&Value=1.99
  • Json: thepage.asp?{"Product":"1","Name":"Coffee","Value":"1.99"}
  • XML: thepage.aps?<xml><Products><product>1</product><name>Coffee</name><Value>1.99</Value></Products>

(Obviouly considering we can’t send special characters via querystring, but I put them here for better understanding)

Which will be the better way (performance, security)?

Thanks in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Based on your comment, you’re limited to what the third-party site will accept – if all it will handle is query-strings, that’s how you’ll have to send it. If it will handle form posts, then you could look at submitting the information in the headers of a post, but that is going to take more work (you also haven’t specified if you’re building a WebRequest on the server side, or doing this through JavaScript on the client side).

    All things considered, here are some general points:

    1. There are various limits on the length of a query string (IE limits them to about 2083 characters, some servers or proxies may ignore parts over 1024 characters etc), while POST requests can be much larger.
    2. If you are doing this client side, the user can see the query string parameters (which has the benefit that they can book mark them), while they can’t (easily) see POST requests.
    3. For greater security, if the third party server supports it, submit the request over SSL.
    4. Special characters can easily be sent via the query string if you UrlEncode them first.

    As to performance, it depends on the amount of processing you have to do to create the query strings over creating XML or JSON strings.

    • 0