Its so happening that my actual data is 1/4 that of the HTTP request header size in bytes.
Is there a way to cut down on the size on the HTTP headers or any other relevant way to deal with this situation?
I am sending data from a mobile device over GPRS to the server and dont want to be burdened with huge request packets that will eat into my $$ and also bandwidth.
Well, what's taking up the bulk of your headers? For example, Stack Overflow recently moved most of the static content to another domain so that the SO cookies wouldn't be included in requests for the static content (which wouldn't use the cookies anyway).
If, however, most of the headers are just things the browser will always send (user agent etc) then there's not a lot you can do.
I've never had to optimize site performance by chopping off headers. That said, most of the issues had to do with:
If you still need better performance after #3, your application needs some form of performance design review.
I consider the headers as "Architecture", that is: "their exact content vary from application to application according to the requirements".
Once you have the exact current list, using the links provided in this post,
you can see which ones you need, and avoid sending the others.
Who knows if it makes a significant difference, but at least you can rest assured that you made your best on that topic.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With