My advice: forget the word "Senior." They're looking for a developer with
something resembling a track record. Failing that, they'll look for a
developer with a good approach to solving the problem the program is
designed to solve.
If you want to gain experience, you can contribute to an open s
When I change to a different URI (https://foo.com/bar) it works as
expected. So there's something with the original response that causes this
to not work. I'm curious as to what, but this is working as designed and
expected.
Thank you for the help!
--
You received this message because you are
Interesting. No headers coming back.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web
.98 is the client, .36 is the server.
This is the end of one transaction and the beginning of another. The client
sends a FIN-ACK, then immediately starts the next transaction with the SYN
packet. After that, the connection is ended; it looks like the client sends
the RST packet. I'll take a
This is what I did, and see no change in behavior.
for i := 0; i < 10; i++ {
response, err :=client.Get("https://foo.com";)
if err!= nil{
panic(err)
}
ioutil.ReadAll(response.Body)
response.Body.Close()
}
The network trace shows a SYN, SYN-ACK, ACK at the beginning of
I wrote a small program that runs a repeated GET against a given URL.
However, the DisableKeepAlives boolean does not seem to be honored. Code is
similar to this:
transport := &http.Transport{
DisableKeepAlives: false,
}
client := &http.Client{
Transport: transport,
}
for i := 0; i < 1
