You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.9.2 windows/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\Michael\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
What did you do?
when using net/http/cookiejar - the cookie jar works and sends out cookies that is receives in subsequent requests - however, on those subsequent requests, httputil.DumpRequestOut does not show the Cookie header - it shows all the other headers that were sent - just not Cookie
I verified the exact headers sent on the server to make sure it was indeed sending the Cookie header
this is obviously not a critical issue - but figured I would pass it along
What did you expect to see?
Per the docs on httputil.DumpRequestOut, I expected to see all headers which were sent
What did you see instead?
All headers sent, except the Cookie header
The text was updated successfully, but these errors were encountered:
Sorry - upon further investigation.. it does show the Cookie header - but only if you call httputil.DumpRequestOut after executing the request and getting the response - which is fine. I thought httputil.DumpRequestOut should know what headers it was going to send before sending them, but it does not work that way with a cookie jar evidently.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.9.2 windows/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\Michael\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
What did you do?
when using net/http/cookiejar - the cookie jar works and sends out cookies that is receives in subsequent requests - however, on those subsequent requests, httputil.DumpRequestOut does not show the Cookie header - it shows all the other headers that were sent - just not Cookie
I verified the exact headers sent on the server to make sure it was indeed sending the Cookie header
this is obviously not a critical issue - but figured I would pass it along
What did you expect to see?
Per the docs on httputil.DumpRequestOut, I expected to see all headers which were sent
What did you see instead?
All headers sent, except the Cookie header
The text was updated successfully, but these errors were encountered: