Tag: Http

Get/Set HTTP Headers in Go Request

HTTP headers, we all need ’em 😉 Here’s how you can get and set these headers within your Go requests. These include request coming into your router handlers and requests you are sending out to other systems through net/http. This can be thought of as being the same as reading headers from a request and creating new ones. First we’ll start with reading them from the request.

#http#headers#set#get#net#request#handler#router

Get Status Code from HTTP Request

We won’t go into too much detail about HTTP status codes themselves, but in this post we will talk about how to use the status code after making a request, how to check them as a range and how to print them as text. This is often important so we can check if something was successful or failed. You can always get this data if you have a net/http/Response type (spec).

#http#status#code#response#struct#range#net#error#checking

Convert an io.ReadCloser to String

Using Go, we often make HTTP calls these days using net/http, which result in a response of type io.ReadCloser… which are hard to read for the layman (like me). What we really want to the response in the form of a string which we can read. This post will talk about how to convert these ReadCloser into strings. First we’ll look at the problem, then we have two different solutions.

#readcloser#io#convert#string#conversion#ioutil#buffer#memory#http#net

Download a File from a URL

This post shows how you can download a file in Go from a URL. We use the std lib (standard library) http.Get() [docs] and io.Copy() [docs] functions to help us with this. This function should be efficient as it will stream the data into the file, as opposed to downloading it all into memory, then to file. The file will be saved in the same directory as your program. We also show an alternative below if you want to take the filename from the URL.

#download#file#io#copy#http#save#filename#stream

Check If a Go Client Has Reused a Connection

For logging purposes, performance monitoring, debugging - what ever your reason, it can be useful to know if Go has reused it’s connection when making an initial request, for later use. If it’s not reusing connections, it might be running slower and less efficiently than it needs to be. The code below is used as an example of how to log if connections are being reused, as well as outputting the DNS information gathered.

#http#reuse#log#dns#httptrace#tcp#context#request