How to send large text (String) as response from a REST service to REST client in Java?












2















I have a restful application, where I need to send text as response to REST client. Now the problem is that sometimes text could be huge nearly 100000 characters.



Can I send large data as normal, plain text?



How to send it through the network to my REST client?






java rest







share|improve this question

























  • A POST response has generally no size limitations so 100000 characters should not be a problem. There can, however, be a limitation due to the web server and/or implementation you use.

    – T A
    Nov 16 '18 at 12:06






  • 1





    100,000 characters of ASCII text is only 98kB (allow a bit more for unicode) - people transfer much larger chunks of data over the internet all the time (think video)

    – MTCoster
    Nov 16 '18 at 12:10











  • @MTCoster thank you soo much. That is a valid point

    – yatheendra k v
    Nov 16 '18 at 12:35











  • Thanks a lot for the information @TA .It helped to proceed.

    – yatheendra k v
    Nov 16 '18 at 12:38











  • For HTTP connections I'd recommend chuncked transfer encodings, especially for larger payloads, as this allows you to send data to the client continiously and end the stream with a simple 0

    – Roman Vottner
    Nov 16 '18 at 13:08
















2















I have a restful application, where I need to send text as response to REST client. Now the problem is that sometimes text could be huge nearly 100000 characters.



Can I send large data as normal, plain text?



How to send it through the network to my REST client?






java rest







share|improve this question

























  • A POST response has generally no size limitations so 100000 characters should not be a problem. There can, however, be a limitation due to the web server and/or implementation you use.

    – T A
    Nov 16 '18 at 12:06






  • 1





    100,000 characters of ASCII text is only 98kB (allow a bit more for unicode) - people transfer much larger chunks of data over the internet all the time (think video)

    – MTCoster
    Nov 16 '18 at 12:10











  • @MTCoster thank you soo much. That is a valid point

    – yatheendra k v
    Nov 16 '18 at 12:35











  • Thanks a lot for the information @TA .It helped to proceed.

    – yatheendra k v
    Nov 16 '18 at 12:38











  • For HTTP connections I'd recommend chuncked transfer encodings, especially for larger payloads, as this allows you to send data to the client continiously and end the stream with a simple 0

    – Roman Vottner
    Nov 16 '18 at 13:08














2












2








2








I have a restful application, where I need to send text as response to REST client. Now the problem is that sometimes text could be huge nearly 100000 characters.



Can I send large data as normal, plain text?



How to send it through the network to my REST client?






java rest







share|improve this question
















I have a restful application, where I need to send text as response to REST client. Now the problem is that sometimes text could be huge nearly 100000 characters.



Can I send large data as normal, plain text?



How to send it through the network to my REST client?






java rest




java rest






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 16 '18 at 12:41









Karol Dowbecki

26.3k93759




26.3k93759










asked Nov 16 '18 at 11:59









yatheendra k vyatheendra k v

234




234













  • A POST response has generally no size limitations so 100000 characters should not be a problem. There can, however, be a limitation due to the web server and/or implementation you use.

    – T A
    Nov 16 '18 at 12:06






  • 1





    100,000 characters of ASCII text is only 98kB (allow a bit more for unicode) - people transfer much larger chunks of data over the internet all the time (think video)

    – MTCoster
    Nov 16 '18 at 12:10











  • @MTCoster thank you soo much. That is a valid point

    – yatheendra k v
    Nov 16 '18 at 12:35











  • Thanks a lot for the information @TA .It helped to proceed.

    – yatheendra k v
    Nov 16 '18 at 12:38











  • For HTTP connections I'd recommend chuncked transfer encodings, especially for larger payloads, as this allows you to send data to the client continiously and end the stream with a simple 0

    – Roman Vottner
    Nov 16 '18 at 13:08



















  • A POST response has generally no size limitations so 100000 characters should not be a problem. There can, however, be a limitation due to the web server and/or implementation you use.

    – T A
    Nov 16 '18 at 12:06






  • 1





    100,000 characters of ASCII text is only 98kB (allow a bit more for unicode) - people transfer much larger chunks of data over the internet all the time (think video)

    – MTCoster
    Nov 16 '18 at 12:10











  • @MTCoster thank you soo much. That is a valid point

    – yatheendra k v
    Nov 16 '18 at 12:35











  • Thanks a lot for the information @TA .It helped to proceed.

    – yatheendra k v
    Nov 16 '18 at 12:38











  • For HTTP connections I'd recommend chuncked transfer encodings, especially for larger payloads, as this allows you to send data to the client continiously and end the stream with a simple 0

    – Roman Vottner
    Nov 16 '18 at 13:08

















A POST response has generally no size limitations so 100000 characters should not be a problem. There can, however, be a limitation due to the web server and/or implementation you use.

– T A
Nov 16 '18 at 12:06





A POST response has generally no size limitations so 100000 characters should not be a problem. There can, however, be a limitation due to the web server and/or implementation you use.

– T A
Nov 16 '18 at 12:06




1




1





100,000 characters of ASCII text is only 98kB (allow a bit more for unicode) - people transfer much larger chunks of data over the internet all the time (think video)

– MTCoster
Nov 16 '18 at 12:10





100,000 characters of ASCII text is only 98kB (allow a bit more for unicode) - people transfer much larger chunks of data over the internet all the time (think video)

– MTCoster
Nov 16 '18 at 12:10













@MTCoster thank you soo much. That is a valid point

– yatheendra k v
Nov 16 '18 at 12:35





@MTCoster thank you soo much. That is a valid point

– yatheendra k v
Nov 16 '18 at 12:35













Thanks a lot for the information @TA .It helped to proceed.

– yatheendra k v
Nov 16 '18 at 12:38





Thanks a lot for the information @TA .It helped to proceed.

– yatheendra k v
Nov 16 '18 at 12:38













For HTTP connections I'd recommend chuncked transfer encodings, especially for larger payloads, as this allows you to send data to the client continiously and end the stream with a simple 0

– Roman Vottner
Nov 16 '18 at 13:08





For HTTP connections I'd recommend chuncked transfer encodings, especially for larger payloads, as this allows you to send data to the client continiously and end the stream with a simple 0

– Roman Vottner
Nov 16 '18 at 13:08












1 Answer
1






active

oldest

votes


















2














You should use HTTP compression by using Accept-Encoding request header and Content-Encoding response header:



GET /your-url HTTP/1.1

Host: www.example.com

Accept-Encoding: gzip, deflate


This will make the compression transparent for most REST API clients. GZIP should be handled out of the box by most client libraries plus it can be disabled by not setting Accept-Encoding header.






share|improve this answer



















  • 1





    Note that compression over HTTPS can leave you vulnernable to BREACH attacks.

    – Eric Stein
    Nov 16 '18 at 16:36












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53337483%2fhow-to-send-large-text-string-as-response-from-a-rest-service-to-rest-client-i%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














You should use HTTP compression by using Accept-Encoding request header and Content-Encoding response header:



GET /your-url HTTP/1.1

Host: www.example.com

Accept-Encoding: gzip, deflate


This will make the compression transparent for most REST API clients. GZIP should be handled out of the box by most client libraries plus it can be disabled by not setting Accept-Encoding header.






share|improve this answer



















  • 1





    Note that compression over HTTPS can leave you vulnernable to BREACH attacks.

    – Eric Stein
    Nov 16 '18 at 16:36
















2














You should use HTTP compression by using Accept-Encoding request header and Content-Encoding response header:



GET /your-url HTTP/1.1

Host: www.example.com

Accept-Encoding: gzip, deflate


This will make the compression transparent for most REST API clients. GZIP should be handled out of the box by most client libraries plus it can be disabled by not setting Accept-Encoding header.






share|improve this answer



















  • 1





    Note that compression over HTTPS can leave you vulnernable to BREACH attacks.

    – Eric Stein
    Nov 16 '18 at 16:36














2












2








2







You should use HTTP compression by using Accept-Encoding request header and Content-Encoding response header:



GET /your-url HTTP/1.1

Host: www.example.com

Accept-Encoding: gzip, deflate


This will make the compression transparent for most REST API clients. GZIP should be handled out of the box by most client libraries plus it can be disabled by not setting Accept-Encoding header.






share|improve this answer













You should use HTTP compression by using Accept-Encoding request header and Content-Encoding response header:



GET /your-url HTTP/1.1

Host: www.example.com

Accept-Encoding: gzip, deflate


This will make the compression transparent for most REST API clients. GZIP should be handled out of the box by most client libraries plus it can be disabled by not setting Accept-Encoding header.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 16 '18 at 12:07









Karol DowbeckiKarol Dowbecki

26.3k93759




26.3k93759








  • 1





    Note that compression over HTTPS can leave you vulnernable to BREACH attacks.

    – Eric Stein
    Nov 16 '18 at 16:36














  • 1





    Note that compression over HTTPS can leave you vulnernable to BREACH attacks.

    – Eric Stein
    Nov 16 '18 at 16:36








1




1





Note that compression over HTTPS can leave you vulnernable to BREACH attacks.

– Eric Stein
Nov 16 '18 at 16:36





Note that compression over HTTPS can leave you vulnernable to BREACH attacks.

– Eric Stein
Nov 16 '18 at 16:36




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53337483%2fhow-to-send-large-text-string-as-response-from-a-rest-service-to-rest-client-i%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Bressuire

Image
Subprefecture and commune in Nouvelle-Aquitaine, France Bressuire Subprefecture and commune Chateau de Bressuire and the Eglise Notre-Dame Coat of arms Location of Bressuire Bressuire Show map of France Bressuire Show map of Nouvelle-Aquitaine Coordinates: 46°50′27″N 0°29′14″W  /  46.8408°N 0.4872°W  / 46.8408; -0.4872 Coordinates: 46°50′27″N 0°29′14″W  /  46.8408°N 0.4872°W  / 46.8408; -0.4872 Country France Region Nouvelle-Aquitaine Department Deux-Sèvres Arrondissement Bressuire Canton Bressuire Government  • Mayor .mw-parser-output .nobold{font-weight:normal} (2014–20) Jean Michel Bernier Area 1 180.59 km 2 (69.73 sq mi) Population (2014) 2 19,300  • Density 110/km 2 (280/sq mi) Time zone UTC+01:00 (CET)  • Summer (DST) UTC+02:00 (CEST) INSEE/Postal code 79049 /79300 Elevation 98–236 m (322–774 ft) (avg. 173 m or 568 ft) 1 French Land Register data, which exclude...
Read more

Vorschmack

Image
Vorschmack Ukrainian Jewish-style vorschmack served on rye bread Course Hors d'oeuvre Region or state Eastern Europe Associated national cuisine Ashkenazi Jewish, Finnish, German, Ukrainian, Polish, Russian Main ingredients Ground meat and/or fish Cookbook: Vorschmack   Media: Vorschmack Vorschmack or forshmak (Yiddish: פֿאָרשמאַק ‎, from archaic German Vorschmack , "foretaste" [1] or "appetizer" [2] ) is an originally East European dish made of salty minced fish or meat. Different variants of this dish are especially common in Ashkenazi Jewish and Finnish cuisine. Some varieties are also known in Russian and Polish cuisine. Contents 1 In Jewish cuisine 2 In Russian cuisine 3 In Polish cuisine 4 In Finnish cuisine 5 See also 6 References In Jewish cuisine According to Gil Marks, the German name points to the possible Germanic origin of this dish. [1] William Pokhlyobkin descr...
Read more

Quarantine

Image
For other uses, see Quarantine (disambiguation). Signal flag "Lima" called the "Yellow Jack" which when flown in harbor means ship is under quarantine. A simple yellow flag (also called the "Yellow Jack") had historically been used to signal quarantine (it stands for Q among signal flags), but now indicates the opposite, as a signal of a ship free of disease that requests boarding and inspection. A quarantine is used to separate and restrict the movement of people; it is 'a restraint upon the activities or communication of persons or the transport of goods designed to prevent the spread of disease or pests', for a certain period of time. [1] This is often used in connection to disease and illness, such as those who may possibly have been exposed to a communicable disease. [2] The term is often erroneously used to mean medical isolation, which is "to separate ill persons who have a communicable disease from those who are healthy...
Read more