Is splitting http request header meaningful in golang http package?
Most servers have the http request header length limit(4k~8k).
Usually we split the long headers into several parts.
For golang http package, I remember that it combines headers with the same key value into one giant header. Is this correct?
Like if I have a token which length exceeds the 8k limit. I'd like to split into several parts with the same header key Authorization.
Then send request using http package.
Does this split make sense or not?
http go http-headers
add a comment |
Most servers have the http request header length limit(4k~8k).
Usually we split the long headers into several parts.
For golang http package, I remember that it combines headers with the same key value into one giant header. Is this correct?
Like if I have a token which length exceeds the 8k limit. I'd like to split into several parts with the same header key Authorization.
Then send request using http package.
Does this split make sense or not?
http go http-headers
The ReadMIMEHeader documentation describes how multiple headers and headers with continuation lines are handled.
– ThunderCat
Nov 14 '18 at 7:39
add a comment |
Most servers have the http request header length limit(4k~8k).
Usually we split the long headers into several parts.
For golang http package, I remember that it combines headers with the same key value into one giant header. Is this correct?
Like if I have a token which length exceeds the 8k limit. I'd like to split into several parts with the same header key Authorization.
Then send request using http package.
Does this split make sense or not?
http go http-headers
Most servers have the http request header length limit(4k~8k).
Usually we split the long headers into several parts.
For golang http package, I remember that it combines headers with the same key value into one giant header. Is this correct?
Like if I have a token which length exceeds the 8k limit. I'd like to split into several parts with the same header key Authorization.
Then send request using http package.
Does this split make sense or not?
http go http-headers
http go http-headers
asked Nov 14 '18 at 5:21
JoyceLeeJoyceLee
224
224
The ReadMIMEHeader documentation describes how multiple headers and headers with continuation lines are handled.
– ThunderCat
Nov 14 '18 at 7:39
add a comment |
The ReadMIMEHeader documentation describes how multiple headers and headers with continuation lines are handled.
– ThunderCat
Nov 14 '18 at 7:39
The ReadMIMEHeader documentation describes how multiple headers and headers with continuation lines are handled.
– ThunderCat
Nov 14 '18 at 7:39
The ReadMIMEHeader documentation describes how multiple headers and headers with continuation lines are handled.
– ThunderCat
Nov 14 '18 at 7:39
add a comment |
1 Answer
1
active
oldest
votes
Hmm, I'm not sure that's quite valid. The Headers object is actually a map of string keys pointing to string slices.
https://golang.org/pkg/net/http/#Header
As such, if you try to set the same key it will be overwritten as per standard golang map functionality.
1
The net/http server appends to the slice. It does not replace the slice.
– ThunderCat
Nov 14 '18 at 7:33
1
It's a map to slice of strings precisely to support repeated keys: play.golang.org/p/jdCBw2fIXHF.
– Peter
Nov 14 '18 at 7:55
Gah, sorry folks. :/
– sebito91
Nov 15 '18 at 17:34
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53293642%2fis-splitting-http-request-header-meaningful-in-golang-http-package%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
Hmm, I'm not sure that's quite valid. The Headers object is actually a map of string keys pointing to string slices.
https://golang.org/pkg/net/http/#Header
As such, if you try to set the same key it will be overwritten as per standard golang map functionality.
1
The net/http server appends to the slice. It does not replace the slice.
– ThunderCat
Nov 14 '18 at 7:33
1
It's a map to slice of strings precisely to support repeated keys: play.golang.org/p/jdCBw2fIXHF.
– Peter
Nov 14 '18 at 7:55
Gah, sorry folks. :/
– sebito91
Nov 15 '18 at 17:34
add a comment |
Hmm, I'm not sure that's quite valid. The Headers object is actually a map of string keys pointing to string slices.
https://golang.org/pkg/net/http/#Header
As such, if you try to set the same key it will be overwritten as per standard golang map functionality.
1
The net/http server appends to the slice. It does not replace the slice.
– ThunderCat
Nov 14 '18 at 7:33
1
It's a map to slice of strings precisely to support repeated keys: play.golang.org/p/jdCBw2fIXHF.
– Peter
Nov 14 '18 at 7:55
Gah, sorry folks. :/
– sebito91
Nov 15 '18 at 17:34
add a comment |
Hmm, I'm not sure that's quite valid. The Headers object is actually a map of string keys pointing to string slices.
https://golang.org/pkg/net/http/#Header
As such, if you try to set the same key it will be overwritten as per standard golang map functionality.
Hmm, I'm not sure that's quite valid. The Headers object is actually a map of string keys pointing to string slices.
https://golang.org/pkg/net/http/#Header
As such, if you try to set the same key it will be overwritten as per standard golang map functionality.
answered Nov 14 '18 at 6:31
sebito91sebito91
1105
1105
1
The net/http server appends to the slice. It does not replace the slice.
– ThunderCat
Nov 14 '18 at 7:33
1
It's a map to slice of strings precisely to support repeated keys: play.golang.org/p/jdCBw2fIXHF.
– Peter
Nov 14 '18 at 7:55
Gah, sorry folks. :/
– sebito91
Nov 15 '18 at 17:34
add a comment |
1
The net/http server appends to the slice. It does not replace the slice.
– ThunderCat
Nov 14 '18 at 7:33
1
It's a map to slice of strings precisely to support repeated keys: play.golang.org/p/jdCBw2fIXHF.
– Peter
Nov 14 '18 at 7:55
Gah, sorry folks. :/
– sebito91
Nov 15 '18 at 17:34
1
1
The net/http server appends to the slice. It does not replace the slice.
– ThunderCat
Nov 14 '18 at 7:33
The net/http server appends to the slice. It does not replace the slice.
– ThunderCat
Nov 14 '18 at 7:33
1
1
It's a map to slice of strings precisely to support repeated keys: play.golang.org/p/jdCBw2fIXHF.
– Peter
Nov 14 '18 at 7:55
It's a map to slice of strings precisely to support repeated keys: play.golang.org/p/jdCBw2fIXHF.
– Peter
Nov 14 '18 at 7:55
Gah, sorry folks. :/
– sebito91
Nov 15 '18 at 17:34
Gah, sorry folks. :/
– sebito91
Nov 15 '18 at 17:34
add a comment |
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53293642%2fis-splitting-http-request-header-meaningful-in-golang-http-package%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
The ReadMIMEHeader documentation describes how multiple headers and headers with continuation lines are handled.
– ThunderCat
Nov 14 '18 at 7:39