Over a million developers have joined DZone.
Silver Partner

Sending Data to the Server with HTTP? Size Matters

· Performance Zone

The Performance Zone is brought to you in partnership with Smartbear. Learn more about how the performance of your API's, web, and mobile applications have a direct impact on your bottom line with the Guide to Synthetic Monitoring.

A few times a month I run into someone having issues with this and just a few minutes ago I helped someone out so I thought I'd write something up quickly to help make it (hopefully) a bit more Google-friendly for those having trouble.

The problem, and solution, is typically pretty simple. If you have found that your network calls to send data to the server are failing, check to see if you are doing a GET request. While according to Stack Overflow there is no real limit to the size of a GET request, there are practical and browser-specific limits that may impact you.

In general, if I'm building a form with a text area, I'll use a POST instead of a GET. If I'm sending a file than I'm definitely using POST.

To be clear, this isn't an "Ajax" issue, but a HTTP thing. The person who emailed me today was actually using the HTTPService in Flex.

I'll also add - it's probably a good idea to really think about how much data your user is sending to your server. Are there things you can do to minimize the size? Are you handling timeouts or other errors? On the server, are you checking how much free space you have available? Have you considered using S3 to bypass artificial limits on storage?

The Performance Zone is brought to you in partnership with Smartbear. Discover how important it is to recognize the inherent power of APIs and bulding the appropriate safeguards to protect it with the Essential Guide to API Monitoring.

Topics:

Published at DZone with permission of Raymond Camden , DZone MVB .

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}