Namespace: go.std.net.http
v1.0Contents
Summary
Provides a low-level interface to the net/http package.
Package http provides HTTP client and server implementations.
Get, Head, Post, and PostForm make HTTP (or HTTPS) requests:
resp, err := http.Get("http://example.com/")
...
resp, err := http.Post("http://example.com/upload", "image/jpeg", &buf)
...
resp, err := http.PostForm("http://example.com/form",
url.Values{"key": {"Value"}, "id": {"123"}})
The client must close the response body when finished with it:
resp, err := http.Get("http://example.com/")
if err != nil {
// handle error
}
defer resp.Body.Close()
body, err := io.ReadAll(resp.Body)
// ...
For control over HTTP client headers, redirect policy, and other
settings, create a Client:
client := &http.Client{
CheckRedirect: redirectPolicyFunc,
}
resp, err := client.Get("http://example.com")
// ...
req, err := http.NewRequest("GET", "http://example.com", nil)
// ...
req.Header.Add("If-None-Match", `W/"wyzzy"`)
resp, err := client.Do(req)
// ...
For control over proxies, TLS configuration, keep-alives,
compression, and other settings, create a Transport:
tr := &http.Transport{
MaxIdleConns: 10,
IdleConnTimeout: 30 * time.Second,
DisableCompression: true,
}
client := &http.Client{Transport: tr}
resp, err := client.Get("https://example.com")
Clients and Transports are safe for concurrent use by multiple
goroutines and for efficiency should only be created once and re-used.
ListenAndServe starts an HTTP server with a given address and handler.
The handler is usually nil, which means to use DefaultServeMux.
Handle and HandleFunc add handlers to DefaultServeMux:
http.Handle("/foo", fooHandler)
http.HandleFunc("/bar", func(w http.ResponseWriter, r *http.Request) {
fmt.Fprintf(w, "Hello, %q", html.EscapeString(r.URL.Path))
})
log.Fatal(http.ListenAndServe(":8080", nil))
More control over the server's behavior is available by creating a
custom Server:
s := &http.Server{
Addr: ":8080",
Handler: myHandler,
ReadTimeout: 10 * time.Second,
WriteTimeout: 10 * time.Second,
MaxHeaderBytes: 1 << 20,
}
log.Fatal(s.ListenAndServe())
Starting with Go 1.6, the http package has transparent support for the
HTTP/2 protocol when using HTTPS. Programs that must disable HTTP/2
can do so by setting Transport.TLSNextProto (for clients) or
Server.TLSNextProto (for servers) to a non-nil, empty
map. Alternatively, the following GODEBUG environment variables are
currently supported:
GODEBUG=http2client=0 # disable HTTP/2 client support
GODEBUG=http2server=0 # disable HTTP/2 server support
GODEBUG=http2debug=1 # enable verbose HTTP/2 debug logs
GODEBUG=http2debug=2 # ... even more verbose, with frame dumps
The GODEBUG variables are not covered by Go's API compatibility
promise. Please report any issues before disabling HTTP/2
support: https://golang.org/s/http2bug
The http package's Transport and Server both automatically enable
HTTP/2 support for simple configurations. To enable HTTP/2 for more
complex configurations, to use lower-level HTTP/2 features, or to use
a newer version of Go's http2 package, import "golang.org/x/net/http2"
directly and use its ConfigureTransport and/or ConfigureServer
functions. Manually configuring HTTP/2 via the golang.org/x/net/http2
package takes precedence over the net/http package's built-in HTTP/2
support.
Index
- *Client
- *ConnState
- *Cookie
- *Dir
- *HandlerFunc
- *Header
- *MaxBytesError
- *ProtocolError
- *PushOptions
- *Request
- *Response
- *SameSite
- *ServeMux
- *Server
- *Transport
- AllowQuerySemicolons
- CanonicalHeaderKey
- Client
- CloseNotifier
- ConnState
- Cookie
- CookieJar
- DefaultClient
- DefaultMaxHeaderBytes
- DefaultMaxIdleConnsPerHost
- DefaultServeMux
- DefaultTransport
- DetectContentType
- Dir
- ErrAbortHandler
- ErrBodyNotAllowed
- ErrBodyReadAfterClose
- ErrContentLength
- ErrHandlerTimeout
- ErrHeaderTooLong
- ErrHijacked
- ErrLineTooLong
- ErrMissingBoundary
- ErrMissingContentLength
- ErrMissingFile
- ErrNoCookie
- ErrNoLocation
- ErrNotMultipart
- ErrNotSupported
- ErrServerClosed
- ErrShortBody
- ErrSkipAltProtocol
- ErrUnexpectedTrailer
- ErrUseLastResponse
- ErrWriteAfterFlush
- Error
- FS
- File
- FileServer
- FileSystem
- Flusher
- Get
- Handle
- Handler
- HandlerFunc
- Head
- Header
- Hijacker
- ListenAndServe
- ListenAndServeTLS
- LocalAddrContextKey
- MaxBytesError
- MaxBytesHandler
- MaxBytesReader
- MethodConnect
- MethodDelete
- MethodGet
- MethodHead
- MethodOptions
- MethodPatch
- MethodPost
- MethodPut
- MethodTrace
- NewFileTransport
- NewRequest
- NewRequestWithContext
- NewServeMux
- NoBody
- NotFound
- NotFoundHandler
- ParseHTTPVersion
- ParseTime
- Post
- PostForm
- ProtocolError
- ProxyFromEnvironment
- PushOptions
- Pusher
- ReadRequest
- ReadResponse
- Redirect
- RedirectHandler
- Request
- Response
- ResponseWriter
- RoundTripper
- SameSite
- SameSiteDefaultMode
- SameSiteLaxMode
- SameSiteNoneMode
- SameSiteStrictMode
- Serve
- ServeContent
- ServeFile
- ServeMux
- ServeTLS
- Server
- ServerContextKey
- SetCookie
- StateActive
- StateClosed
- StateHijacked
- StateIdle
- StateNew
- StatusAccepted
- StatusAlreadyReported
- StatusBadGateway
- StatusBadRequest
- StatusConflict
- StatusContinue
- StatusCreated
- StatusEarlyHints
- StatusExpectationFailed
- StatusFailedDependency
- StatusForbidden
- StatusFound
- StatusGatewayTimeout
- StatusGone
- StatusHTTPVersionNotSupported
- StatusIMUsed
- StatusInsufficientStorage
- StatusInternalServerError
- StatusLengthRequired
- StatusLocked
- StatusLoopDetected
- StatusMethodNotAllowed
- StatusMisdirectedRequest
- StatusMovedPermanently
- StatusMultiStatus
- StatusMultipleChoices
- StatusNetworkAuthenticationRequired
- StatusNoContent
- StatusNonAuthoritativeInfo
- StatusNotAcceptable
- StatusNotExtended
- StatusNotFound
- StatusNotImplemented
- StatusNotModified
- StatusOK
- StatusPartialContent
- StatusPaymentRequired
- StatusPermanentRedirect
- StatusPreconditionFailed
- StatusPreconditionRequired
- StatusProcessing
- StatusProxyAuthRequired
- StatusRequestEntityTooLarge
- StatusRequestHeaderFieldsTooLarge
- StatusRequestTimeout
- StatusRequestURITooLong
- StatusRequestedRangeNotSatisfiable
- StatusResetContent
- StatusSeeOther
- StatusServiceUnavailable
- StatusSwitchingProtocols
- StatusTeapot
- StatusTemporaryRedirect
- StatusText
- StatusTooEarly
- StatusTooManyRequests
- StatusUnauthorized
- StatusUnavailableForLegalReasons
- StatusUnprocessableEntity
- StatusUnsupportedMediaType
- StatusUpgradeRequired
- StatusUseProxy
- StatusVariantAlsoNegotiates
- StripPrefix
- TimeFormat
- TimeoutHandler
- TrailerPrefix
- Transport
- arrayOfClient
- arrayOfCloseNotifier
- arrayOfConnState
- arrayOfCookie
- arrayOfCookieJar
- arrayOfDir
- arrayOfFile
- arrayOfFileSystem
- arrayOfFlusher
- arrayOfHandler
- arrayOfHandlerFunc
- arrayOfHeader
- arrayOfHijacker
- arrayOfMaxBytesError
- arrayOfProtocolError
- arrayOfPushOptions
- arrayOfPusher
- arrayOfRequest
- arrayOfResponse
- arrayOfResponseWriter
- arrayOfRoundTripper
- arrayOfSameSite
- arrayOfServeMux
- arrayOfServer
- arrayOfTransport
Legend
-
Constant
Variable
Function
Macro
Special form
Type
GoVar
Receiver/Method
Constants
Constants are variables with :const true in their metadata. Joker currently does not recognize them as special; as such, it allows redefining them or their values.-
DefaultMaxHeaderBytes
Int v1.01 MB
-
DefaultMaxIdleConnsPerHost
Int v1.0DefaultMaxIdleConnsPerHost is the default value of Transport's
MaxIdleConnsPerHost.
-
MethodConnect
String v1.0Common HTTP methods.
Unless otherwise noted, these are defined in RFC 7231 section 4.3.
-
MethodDelete
String v1.0Common HTTP methods.
Unless otherwise noted, these are defined in RFC 7231 section 4.3.
-
MethodGet
String v1.0Common HTTP methods.
Unless otherwise noted, these are defined in RFC 7231 section 4.3.
-
MethodHead
String v1.0Common HTTP methods.
Unless otherwise noted, these are defined in RFC 7231 section 4.3.
-
MethodOptions
String v1.0Common HTTP methods.
Unless otherwise noted, these are defined in RFC 7231 section 4.3.
-
MethodPatch
String v1.0RFC 5789
-
MethodPost
String v1.0Common HTTP methods.
Unless otherwise noted, these are defined in RFC 7231 section 4.3.
-
MethodPut
String v1.0Common HTTP methods.
Unless otherwise noted, these are defined in RFC 7231 section 4.3.
-
MethodTrace
String v1.0Common HTTP methods.
Unless otherwise noted, these are defined in RFC 7231 section 4.3.
-
StatusAccepted
Int v1.0RFC 9110, 15.3.3
-
StatusAlreadyReported
Int v1.0RFC 5842, 7.1
-
StatusBadGateway
Int v1.0RFC 9110, 15.6.3
-
StatusBadRequest
Int v1.0RFC 9110, 15.5.1
-
StatusConflict
Int v1.0RFC 9110, 15.5.10
-
StatusContinue
Int v1.0RFC 9110, 15.2.1
-
StatusCreated
Int v1.0RFC 9110, 15.3.2
-
StatusEarlyHints
Int v1.0RFC 8297
-
StatusExpectationFailed
Int v1.0RFC 9110, 15.5.18
-
StatusFailedDependency
Int v1.0RFC 4918, 11.4
-
StatusForbidden
Int v1.0RFC 9110, 15.5.4
-
StatusFound
Int v1.0RFC 9110, 15.4.3
-
StatusGatewayTimeout
Int v1.0RFC 9110, 15.6.5
-
StatusGone
Int v1.0RFC 9110, 15.5.11
-
StatusHTTPVersionNotSupported
Int v1.0RFC 9110, 15.6.6
-
StatusIMUsed
Int v1.0RFC 3229, 10.4.1
-
StatusInsufficientStorage
Int v1.0RFC 4918, 11.5
-
StatusInternalServerError
Int v1.0RFC 9110, 15.6.1
-
StatusLengthRequired
Int v1.0RFC 9110, 15.5.12
-
StatusLocked
Int v1.0RFC 4918, 11.3
-
StatusLoopDetected
Int v1.0RFC 5842, 7.2
-
StatusMethodNotAllowed
Int v1.0RFC 9110, 15.5.6
-
StatusMisdirectedRequest
Int v1.0RFC 9110, 15.5.20
-
StatusMovedPermanently
Int v1.0RFC 9110, 15.4.2
-
StatusMultiStatus
Int v1.0RFC 4918, 11.1
-
StatusMultipleChoices
Int v1.0RFC 9110, 15.4.1
-
StatusNetworkAuthenticationRequired
Int v1.0RFC 6585, 6
-
StatusNoContent
Int v1.0RFC 9110, 15.3.5
-
StatusNonAuthoritativeInfo
Int v1.0RFC 9110, 15.3.4
-
StatusNotAcceptable
Int v1.0RFC 9110, 15.5.7
-
StatusNotExtended
Int v1.0RFC 2774, 7
-
StatusNotFound
Int v1.0RFC 9110, 15.5.5
-
StatusNotImplemented
Int v1.0RFC 9110, 15.6.2
-
StatusNotModified
Int v1.0RFC 9110, 15.4.5
-
StatusOK
Int v1.0RFC 9110, 15.3.1
-
StatusPartialContent
Int v1.0RFC 9110, 15.3.7
-
StatusPaymentRequired
Int v1.0RFC 9110, 15.5.3
-
StatusPermanentRedirect
Int v1.0RFC 9110, 15.4.9
-
StatusPreconditionFailed
Int v1.0RFC 9110, 15.5.13
-
StatusPreconditionRequired
Int v1.0RFC 6585, 3
-
StatusProcessing
Int v1.0RFC 2518, 10.1
-
StatusProxyAuthRequired
Int v1.0RFC 9110, 15.5.8
-
StatusRequestEntityTooLarge
Int v1.0RFC 9110, 15.5.14
-
StatusRequestHeaderFieldsTooLarge
Int v1.0RFC 6585, 5
-
StatusRequestTimeout
Int v1.0RFC 9110, 15.5.9
-
StatusRequestURITooLong
Int v1.0RFC 9110, 15.5.15
-
StatusRequestedRangeNotSatisfiable
Int v1.0RFC 9110, 15.5.17
-
StatusResetContent
Int v1.0RFC 9110, 15.3.6
-
StatusSeeOther
Int v1.0RFC 9110, 15.4.4
-
StatusServiceUnavailable
Int v1.0RFC 9110, 15.6.4
-
StatusSwitchingProtocols
Int v1.0RFC 9110, 15.2.2
-
StatusTeapot
Int v1.0RFC 9110, 15.5.19 (Unused)
-
StatusTemporaryRedirect
Int v1.0RFC 9110, 15.4.8
-
StatusTooEarly
Int v1.0RFC 8470, 5.2.
-
StatusTooManyRequests
Int v1.0RFC 6585, 4
-
StatusUnauthorized
Int v1.0RFC 9110, 15.5.2
-
StatusUnavailableForLegalReasons
Int v1.0RFC 7725, 3
-
StatusUnprocessableEntity
Int v1.0RFC 9110, 15.5.21
-
StatusUnsupportedMediaType
Int v1.0RFC 9110, 15.5.16
-
StatusUpgradeRequired
Int v1.0RFC 9110, 15.5.22
-
StatusUseProxy
Int v1.0RFC 9110, 15.4.6
-
StatusVariantAlsoNegotiates
Int v1.0RFC 2295, 8.1
-
TimeFormat
String v1.0TimeFormat is the time format to use when generating times in HTTP
headers. It is like time.RFC1123 but hard-codes GMT as the time
zone. The time being formatted must be in UTC for Format to
generate the correct format.
For parsing this time format, see ParseTime.
-
TrailerPrefix
String v1.0TrailerPrefix is a magic prefix for ResponseWriter.Header map keys
that, if present, signals that the map entry is actually for
the response trailers, and not the response headers. The prefix
is stripped after the ServeHTTP call finishes and the values are
sent in the trailers.
This mechanism is intended only for trailers that are not known
prior to the headers being written. If the set of trailers is fixed
or known before the header is written, the normal Go trailers mechanism
is preferred:
https://pkg.go.dev/net/http#ResponseWriter
https://pkg.go.dev/net/http#example-ResponseWriter-Trailers
Variables
-
DefaultClient
Var v1.0DefaultClient is the default Client and is used by Get, Head, and Post.
-
DefaultServeMux
Var v1.0DefaultServeMux is the default ServeMux used by Serve.
-
DefaultTransport
Var v1.0DefaultTransport is the default implementation of Transport and is
used by DefaultClient. It establishes network connections as needed
and caches them for reuse by subsequent calls. It uses HTTP proxies
as directed by the $HTTP_PROXY and $NO_PROXY (or $http_proxy and
$no_proxy) environment variables.
-
ErrAbortHandler
Var v1.0ErrAbortHandler is a sentinel panic value to abort a handler.
While any panic from ServeHTTP aborts the response to the client,
panicking with ErrAbortHandler also suppresses logging of a stack
trace to the server's error log.
-
ErrBodyNotAllowed
Var v1.0ErrBodyNotAllowed is returned by ResponseWriter.Write calls
when the HTTP method or response code does not permit a
body.
-
ErrBodyReadAfterClose
Var v1.0ErrBodyReadAfterClose is returned when reading a Request or Response
Body after the body has been closed. This typically happens when the body is
read after an HTTP Handler calls WriteHeader or Write on its
ResponseWriter.
-
ErrContentLength
Var v1.0ErrContentLength is returned by ResponseWriter.Write calls
when a Handler set a Content-Length response header with a
declared size and then attempted to write more bytes than
declared.
-
ErrHandlerTimeout
Var v1.0ErrHandlerTimeout is returned on ResponseWriter Write calls
in handlers which have timed out.
-
ErrHeaderTooLong
Var v1.0Deprecated: ErrHeaderTooLong is no longer returned by
anything in the net/http package. Callers should not
compare errors against this variable.
-
ErrHijacked
Var v1.0ErrHijacked is returned by ResponseWriter.Write calls when
the underlying connection has been hijacked using the
Hijacker interface. A zero-byte write on a hijacked
connection will return ErrHijacked without any other side
effects.
-
ErrLineTooLong
Var v1.0ErrLineTooLong is returned when reading request or response bodies
with malformed chunked encoding.
-
ErrMissingBoundary
Var v1.0ErrMissingBoundary is returned by Request.MultipartReader when the
request's Content-Type does not include a "boundary" parameter.
-
ErrMissingContentLength
Var v1.0Deprecated: ErrMissingContentLength is no longer returned by
anything in the net/http package. Callers should not
compare errors against this variable.
-
ErrMissingFile
Var v1.0ErrMissingFile is returned by FormFile when the provided file field name
is either not present in the request or not a file field.
-
ErrNoCookie
Var v1.0ErrNoCookie is returned by Request's Cookie method when a cookie is not found.
-
ErrNoLocation
Var v1.0ErrNoLocation is returned by Response's Location method
when no Location header is present.
-
ErrNotMultipart
Var v1.0ErrNotMultipart is returned by Request.MultipartReader when the
request's Content-Type is not multipart/form-data.
-
ErrNotSupported
Var v1.0ErrNotSupported is returned by the Push method of Pusher
implementations to indicate that HTTP/2 Push support is not
available.
-
ErrServerClosed
Var v1.0ErrServerClosed is returned by the Server's Serve, ServeTLS, ListenAndServe,
and ListenAndServeTLS methods after a call to Shutdown or Close.
-
ErrShortBody
Var v1.0Deprecated: ErrShortBody is no longer returned by
anything in the net/http package. Callers should not
compare errors against this variable.
-
ErrSkipAltProtocol
Var v1.0ErrSkipAltProtocol is a sentinel error value defined by Transport.RegisterProtocol.
-
ErrUnexpectedTrailer
Var v1.0Deprecated: ErrUnexpectedTrailer is no longer returned by
anything in the net/http package. Callers should not
compare errors against this variable.
-
ErrUseLastResponse
Var v1.0ErrUseLastResponse can be returned by Client.CheckRedirect hooks to
control how redirects are processed. If returned, the next request
is not sent and the most recent response is returned with its body
unclosed.
-
ErrWriteAfterFlush
Var v1.0Deprecated: ErrWriteAfterFlush is no longer returned by
anything in the net/http package. Callers should not
compare errors against this variable.
-
LocalAddrContextKey
Var v1.0LocalAddrContextKey is a context key. It can be used in
HTTP handlers with Context.Value to access the local
address the connection arrived on.
The associated value will be of type net.Addr.
-
NoBody
Var v1.0NoBody is an io.ReadCloser with no bytes. Read always returns EOF
and Close always returns nil. It can be used in an outgoing client
request to explicitly signal that a request has zero bytes.
An alternative, however, is to simply set Request.Body to nil.
-
SameSiteDefaultMode
GoObject v1.0 -
SameSiteLaxMode
GoObject v1.0 -
SameSiteNoneMode
GoObject v1.0 -
SameSiteStrictMode
GoObject v1.0 -
ServerContextKey
Var v1.0ServerContextKey is a context key. It can be used in HTTP
handlers with Context.Value to access the server that
started the handler. The associated value will be of
type *Server.
-
StateActive
GoObject v1.0StateActive represents a connection that has read 1 or more
bytes of a request. The Server.ConnState hook for
StateActive fires before the request has entered a handler
and doesn't fire again until the request has been
handled. After the request is handled, the state
transitions to StateClosed, StateHijacked, or StateIdle.
For HTTP/2, StateActive fires on the transition from zero
to one active request, and only transitions away once all
active requests are complete. That means that ConnState
cannot be used to do per-request work; ConnState only notes
the overall state of the connection.
-
StateClosed
GoObject v1.0StateClosed represents a closed connection.
This is a terminal state. Hijacked connections do not
transition to StateClosed.
-
StateHijacked
GoObject v1.0StateHijacked represents a hijacked connection.
This is a terminal state. It does not transition to StateClosed.
-
StateIdle
GoObject v1.0StateIdle represents a connection that has finished
handling a request and is in the keep-alive state, waiting
for a new request. Connections transition from StateIdle
to either StateActive or StateClosed.
-
StateNew
GoObject v1.0StateNew represents a new connection that is expected to
send a request immediately. Connections begin at this
state and then transition to either StateActive or
StateClosed.
Functions, Macros, and Special Forms
-
AllowQuerySemicolons
Function v1.0(AllowQuerySemicolons h)
AllowQuerySemicolons returns a handler that serves requests by converting any
unescaped semicolons in the URL query to ampersands, and invoking the handler h.
This restores the pre-Go 1.17 behavior of splitting query parameters on both
semicolons and ampersands. (See golang.org/issue/25192). Note that this
behavior doesn't match that of many proxies, and the mismatch can lead to
security issues.
AllowQuerySemicolons should be invoked before Request.ParseForm is called.
Go input arguments: (h Handler)
Go returns: Handler
Joker input arguments: [^Handler h]
Joker returns: ^Handler -
CanonicalHeaderKey
Function v1.0(CanonicalHeaderKey s)
CanonicalHeaderKey returns the canonical format of the
header key s. The canonicalization converts the first
letter and any letter following a hyphen to upper case;
the rest are converted to lowercase. For example, the
canonical key for "accept-encoding" is "Accept-Encoding".
If s contains a space or invalid header field bytes, it is
returned without modifications.
Go input arguments: (s string)
Go returns: string
Joker input arguments: [^String s]
Joker returns: ^String -
DetectContentType
Function v1.0(DetectContentType data)
DetectContentType implements the algorithm described
at https://mimesniff.spec.whatwg.org/ to determine the
Content-Type of the given data. It considers at most the
first 512 bytes of data. DetectContentType always returns
a valid MIME type: if it cannot determine a more specific one, it
returns "application/octet-stream".
Go input arguments: (data []byte)
Go returns: string
Joker input arguments: [^arrayOfByte data]
Joker returns: ^String -
Error
Function v1.0(Error w error code)
Error replies to the request with the specified error message and HTTP code.
It does not otherwise end the request; the caller should ensure no further
writes are done to w.
The error message should be plain text.
Go input arguments: (w ResponseWriter, error string, code int)
Joker input arguments: [^ResponseWriter w, ^String error, ^Int code] -
FS
Function v1.0(FS fsys)
FS converts fsys to a FileSystem implementation,
for use with FileServer and NewFileTransport.
Go input arguments: (fsys io/fs.FS)
Go returns: FileSystem
Joker input arguments: [^go.std.io.fs/FS fsys]
Joker returns: ^FileSystem -
FileServer
Function v1.0(FileServer root)
FileServer returns a handler that serves HTTP requests
with the contents of the file system rooted at root.
As a special case, the returned file server redirects any request
ending in "/index.html" to the same path, without the final
"index.html".
To use the operating system's file system implementation,
use http.Dir:
http.Handle("/", http.FileServer(http.Dir("/tmp")))
To use an fs.FS implementation, use http.FS to convert it:
http.Handle("/", http.FileServer(http.FS(fsys)))
Go input arguments: (root FileSystem)
Go returns: Handler
Joker input arguments: [^FileSystem root]
Joker returns: ^Handler -
Get
Function v1.0(Get url)
Get issues a GET to the specified URL. If the response is one of
the following redirect codes, Get follows the redirect, up to a
maximum of 10 redirects:
301 (Moved Permanently)
302 (Found)
303 (See Other)
307 (Temporary Redirect)
308 (Permanent Redirect)
An error is returned if there were too many redirects or if there
was an HTTP protocol error. A non-2xx response doesn't cause an
error. Any returned error will be of type *url.Error. The url.Error
value's Timeout method will report true if the request timed out.
When err is nil, resp always contains a non-nil resp.Body.
Caller should close resp.Body when done reading from it.
Get is a wrapper around DefaultClient.Get.
To make a request with custom headers, use NewRequest and
DefaultClient.Do.
To make a request with a specified context.Context, use NewRequestWithContext
and DefaultClient.Do.
Go input arguments: (url string)
Go returns: (resp *Response, err error)
Joker input arguments: [^String url]
Joker returns: [^*Response resp, ^Error err] -
Handle
Function v1.0(Handle pattern handler)
Handle registers the handler for the given pattern
in the DefaultServeMux.
The documentation for ServeMux explains how patterns are matched.
Go input arguments: (pattern string, handler Handler)
Joker input arguments: [^String pattern, ^Handler handler] -
Head
Function v1.0(Head url)
Head issues a HEAD to the specified URL. If the response is one of
the following redirect codes, Head follows the redirect, up to a
maximum of 10 redirects:
301 (Moved Permanently)
302 (Found)
303 (See Other)
307 (Temporary Redirect)
308 (Permanent Redirect)
Head is a wrapper around DefaultClient.Head.
To make a request with a specified context.Context, use NewRequestWithContext
and DefaultClient.Do.
Go input arguments: (url string)
Go returns: (resp *Response, err error)
Joker input arguments: [^String url]
Joker returns: [^*Response resp, ^Error err] -
ListenAndServe
Function v1.0(ListenAndServe addr handler)
ListenAndServe listens on the TCP network address addr and then calls
Serve with handler to handle requests on incoming connections.
Accepted connections are configured to enable TCP keep-alives.
The handler is typically nil, in which case the DefaultServeMux is used.
ListenAndServe always returns a non-nil error.
Go input arguments: (addr string, handler Handler)
Go returns: error
Joker input arguments: [^String addr, ^Handler handler]
Joker returns: ^Error -
ListenAndServeTLS
Function v1.0(ListenAndServeTLS addr certFile keyFile handler)
ListenAndServeTLS acts identically to ListenAndServe, except that it
expects HTTPS connections. Additionally, files containing a certificate and
matching private key for the server must be provided. If the certificate
is signed by a certificate authority, the certFile should be the concatenation
of the server's certificate, any intermediates, and the CA's certificate.
Go input arguments: (addr string, certFile string, keyFile string, handler Handler)
Go returns: error
Joker input arguments: [^String addr, ^String certFile, ^String keyFile, ^Handler handler]
Joker returns: ^Error -
MaxBytesHandler
Function v1.0(MaxBytesHandler h n)
MaxBytesHandler returns a Handler that runs h with its ResponseWriter and Request.Body wrapped by a MaxBytesReader.
Go input arguments: (h Handler, n int64)
Go returns: Handler
Joker input arguments: [^Handler h, ^BigInt n]
Joker returns: ^Handler -
MaxBytesReader
Function v1.0(MaxBytesReader w r n)
MaxBytesReader is similar to io.LimitReader but is intended for
limiting the size of incoming request bodies. In contrast to
io.LimitReader, MaxBytesReader's result is a ReadCloser, returns a
non-nil error of type *MaxBytesError for a Read beyond the limit,
and closes the underlying reader when its Close method is called.
MaxBytesReader prevents clients from accidentally or maliciously
sending a large request and wasting server resources. If possible,
it tells the ResponseWriter to close the connection after the limit
has been reached.
Go input arguments: (w ResponseWriter, r io.ReadCloser, n int64)
Go returns: io.ReadCloser
Joker input arguments: [^ResponseWriter w, ^go.std.io/ReadCloser r, ^BigInt n]
Joker returns: ^go.std.io/ReadCloser -
NewFileTransport
Function v1.0(NewFileTransport fs)
NewFileTransport returns a new RoundTripper, serving the provided
FileSystem. The returned RoundTripper ignores the URL host in its
incoming requests, as well as most other properties of the
request.
The typical use case for NewFileTransport is to register the "file"
protocol with a Transport, as in:
t := &http.Transport{}
t.RegisterProtocol("file", http.NewFileTransport(http.Dir("/")))
c := &http.Client{Transport: t}
res, err := c.Get("file:///etc/passwd")
...
Go input arguments: (fs FileSystem)
Go returns: RoundTripper
Joker input arguments: [^FileSystem fs]
Joker returns: ^RoundTripper -
NewRequest
Function v1.0(NewRequest method url body)
NewRequest wraps NewRequestWithContext using context.Background.
Go input arguments: (method string, url string, body io.Reader)
Go returns: (*Request, error)
Joker input arguments: [^String method, ^String url, ^go.std.io/Reader body]
Joker returns: [^*Request, ^Error] -
NewRequestWithContext
Function v1.0(NewRequestWithContext ctx method url body)
NewRequestWithContext returns a new Request given a method, URL, and
optional body.
If the provided body is also an io.Closer, the returned
Request.Body is set to body and will be closed by the Client
methods Do, Post, and PostForm, and Transport.RoundTrip.
NewRequestWithContext returns a Request suitable for use with
Client.Do or Transport.RoundTrip. To create a request for use with
testing a Server Handler, either use the NewRequest function in the
net/http/httptest package, use ReadRequest, or manually update the
Request fields. For an outgoing client request, the context
controls the entire lifetime of a request and its response:
obtaining a connection, sending the request, and reading the
response headers and body. See the Request type's documentation for
the difference between inbound and outbound request fields.
If body is of type *bytes.Buffer, *bytes.Reader, or
*strings.Reader, the returned request's ContentLength is set to its
exact value (instead of -1), GetBody is populated (so 307 and 308
redirects can replay the body), and Body is set to NoBody if the
ContentLength is 0.
Go input arguments: (ctx context.Context, method string, url string, body io.Reader)
Go returns: (*Request, error)
Joker input arguments: [^go.std.context/Context ctx, ^String method, ^String url, ^go.std.io/Reader body]
Joker returns: [^*Request, ^Error] -
NewServeMux
Function v1.0(NewServeMux)
NewServeMux allocates and returns a new ServeMux.
Go returns: *ServeMux
Joker input arguments: []
Joker returns: ^*ServeMux -
NotFound
Function v1.0(NotFound w r)
NotFound replies to the request with an HTTP 404 not found error.
Go input arguments: (w ResponseWriter, r *Request)
Joker input arguments: [^ResponseWriter w, ^*Request r] -
NotFoundHandler
Function v1.0(NotFoundHandler)
NotFoundHandler returns a simple request handler
that replies to each request with a “404 page not found” reply.
Go returns: Handler
Joker input arguments: []
Joker returns: ^Handler -
ParseHTTPVersion
Function v1.0(ParseHTTPVersion vers)
ParseHTTPVersion parses an HTTP version string according to RFC 7230, section 2.6.
"HTTP/1.0" returns (1, 0, true). Note that strings without
a minor version, such as "HTTP/2", are not valid.
Go input arguments: (vers string)
Go returns: (major int, minor int, ok bool)
Joker input arguments: [^String vers]
Joker returns: [^Int major, ^Int minor, ^Boolean ok] -
ParseTime
Function v1.0(ParseTime text)
ParseTime parses a time header (such as the Date: header),
trying each of the three formats allowed by HTTP/1.1:
TimeFormat, time.RFC850, and time.ANSIC.
Go input arguments: (text string)
Go returns: (t time.Time, err error)
Joker input arguments: [^String text]
Joker returns: [^go.std.time/Time t, ^Error err] -
Post
Function v1.0(Post url contentType body)
Post issues a POST to the specified URL.
Caller should close resp.Body when done reading from it.
If the provided body is an io.Closer, it is closed after the
request.
Post is a wrapper around DefaultClient.Post.
To set custom headers, use NewRequest and DefaultClient.Do.
See the Client.Do method documentation for details on how redirects
are handled.
To make a request with a specified context.Context, use NewRequestWithContext
and DefaultClient.Do.
Go input arguments: (url string, contentType string, body io.Reader)
Go returns: (resp *Response, err error)
Joker input arguments: [^String url, ^String contentType, ^go.std.io/Reader body]
Joker returns: [^*Response resp, ^Error err] -
PostForm
Function v1.0(PostForm url data)
PostForm issues a POST to the specified URL, with data's keys and
values URL-encoded as the request body.
The Content-Type header is set to application/x-www-form-urlencoded.
To set other headers, use NewRequest and DefaultClient.Do.
When err is nil, resp always contains a non-nil resp.Body.
Caller should close resp.Body when done reading from it.
PostForm is a wrapper around DefaultClient.PostForm.
See the Client.Do method documentation for details on how redirects
are handled.
To make a request with a specified context.Context, use NewRequestWithContext
and DefaultClient.Do.
Go input arguments: (url string, data net/url.Values)
Go returns: (resp *Response, err error)
Joker input arguments: [^String url, ^go.std.net.url/Values data]
Joker returns: [^*Response resp, ^Error err] -
ProxyFromEnvironment
Function v1.0(ProxyFromEnvironment req)
ProxyFromEnvironment returns the URL of the proxy to use for a
given request, as indicated by the environment variables
HTTP_PROXY, HTTPS_PROXY and NO_PROXY (or the lowercase versions
thereof). HTTPS_PROXY takes precedence over HTTP_PROXY for https
requests.
The environment values may be either a complete URL or a
"host[:port]", in which case the "http" scheme is assumed.
The schemes "http", "https", and "socks5" are supported.
An error is returned if the value is a different form.
A nil URL and nil error are returned if no proxy is defined in the
environment, or a proxy should not be used for the given request,
as defined by NO_PROXY.
As a special case, if req.URL.Host is "localhost" (with or without
a port number), then a nil URL and nil error will be returned.
Go input arguments: (req *Request)
Go returns: (*net/url.URL, error)
Joker input arguments: [^*Request req]
Joker returns: [^go.std.net.url/*URL, ^Error] -
ReadRequest
Function v1.0(ReadRequest b)
ReadRequest reads and parses an incoming request from b.
ReadRequest is a low-level function and should only be used for
specialized applications; most code should use the Server to read
requests and handle them via the Handler interface. ReadRequest
only supports HTTP/1.x requests. For HTTP/2, use golang.org/x/net/http2.
Go input arguments: (b *bufio.Reader)
Go returns: (*Request, error)
Joker input arguments: [^go.std.bufio/*Reader b]
Joker returns: [^*Request, ^Error] -
ReadResponse
Function v1.0(ReadResponse r req)
ReadResponse reads and returns an HTTP response from r.
The req parameter optionally specifies the Request that corresponds
to this Response. If nil, a GET request is assumed.
Clients must call resp.Body.Close when finished reading resp.Body.
After that call, clients can inspect resp.Trailer to find key/value
pairs included in the response trailer.
Go input arguments: (r *bufio.Reader, req *Request)
Go returns: (*Response, error)
Joker input arguments: [^go.std.bufio/*Reader r, ^*Request req]
Joker returns: [^*Response, ^Error] -
Redirect
Function v1.0(Redirect w r url code)
Redirect replies to the request with a redirect to url,
which may be a path relative to the request path.
The provided code should be in the 3xx range and is usually
StatusMovedPermanently, StatusFound or StatusSeeOther.
If the Content-Type header has not been set, Redirect sets it
to "text/html; charset=utf-8" and writes a small HTML body.
Setting the Content-Type header to any value, including nil,
disables that behavior.
Go input arguments: (w ResponseWriter, r *Request, url string, code int)
Joker input arguments: [^ResponseWriter w, ^*Request r, ^String url, ^Int code] -
RedirectHandler
Function v1.0(RedirectHandler url code)
RedirectHandler returns a request handler that redirects
each request it receives to the given url using the given
status code.
The provided code should be in the 3xx range and is usually
StatusMovedPermanently, StatusFound or StatusSeeOther.
Go input arguments: (url string, code int)
Go returns: Handler
Joker input arguments: [^String url, ^Int code]
Joker returns: ^Handler -
Serve
Function v1.0(Serve l handler)
Serve accepts incoming HTTP connections on the listener l,
creating a new service goroutine for each. The service goroutines
read requests and then call handler to reply to them.
The handler is typically nil, in which case the DefaultServeMux is used.
HTTP/2 support is only enabled if the Listener returns *tls.Conn
connections and they were configured with "h2" in the TLS
Config.NextProtos.
Serve always returns a non-nil error.
Go input arguments: (l net.Listener, handler Handler)
Go returns: error
Joker input arguments: [^go.std.net/Listener l, ^Handler handler]
Joker returns: ^Error -
ServeContent
Function v1.0(ServeContent w req name modtime content)
ServeContent replies to the request using the content in the
provided ReadSeeker. The main benefit of ServeContent over io.Copy
is that it handles Range requests properly, sets the MIME type, and
handles If-Match, If-Unmodified-Since, If-None-Match, If-Modified-Since,
and If-Range requests.
If the response's Content-Type header is not set, ServeContent
first tries to deduce the type from name's file extension and,
if that fails, falls back to reading the first block of the content
and passing it to DetectContentType.
The name is otherwise unused; in particular it can be empty and is
never sent in the response.
If modtime is not the zero time or Unix epoch, ServeContent
includes it in a Last-Modified header in the response. If the
request includes an If-Modified-Since header, ServeContent uses
modtime to decide whether the content needs to be sent at all.
The content's Seek method must work: ServeContent uses
a seek to the end of the content to determine its size.
If the caller has set w's ETag header formatted per RFC 7232, section 2.3,
ServeContent uses it to handle requests using If-Match, If-None-Match, or If-Range.
Note that *os.File implements the io.ReadSeeker interface.
Go input arguments: (w ResponseWriter, req *Request, name string, modtime time.Time, content io.ReadSeeker)
Joker input arguments: [^ResponseWriter w, ^*Request req, ^String name, ^go.std.time/Time modtime, ^go.std.io/ReadSeeker content] -
ServeFile
Function v1.0(ServeFile w r name)
ServeFile replies to the request with the contents of the named
file or directory.
If the provided file or directory name is a relative path, it is
interpreted relative to the current directory and may ascend to
parent directories. If the provided name is constructed from user
input, it should be sanitized before calling ServeFile.
As a precaution, ServeFile will reject requests where r.URL.Path
contains a ".." path element; this protects against callers who
might unsafely use filepath.Join on r.URL.Path without sanitizing
it and then use that filepath.Join result as the name argument.
As another special case, ServeFile redirects any request where r.URL.Path
ends in "/index.html" to the same path, without the final
"index.html". To avoid such redirects either modify the path or
use ServeContent.
Outside of those two special cases, ServeFile does not use
r.URL.Path for selecting the file or directory to serve; only the
file or directory provided in the name argument is used.
Go input arguments: (w ResponseWriter, r *Request, name string)
Joker input arguments: [^ResponseWriter w, ^*Request r, ^String name] -
ServeTLS
Function v1.0(ServeTLS l handler certFile keyFile)
ServeTLS accepts incoming HTTPS connections on the listener l,
creating a new service goroutine for each. The service goroutines
read requests and then call handler to reply to them.
The handler is typically nil, in which case the DefaultServeMux is used.
Additionally, files containing a certificate and matching private key
for the server must be provided. If the certificate is signed by a
certificate authority, the certFile should be the concatenation
of the server's certificate, any intermediates, and the CA's certificate.
ServeTLS always returns a non-nil error.
Go input arguments: (l net.Listener, handler Handler, certFile string, keyFile string)
Go returns: error
Joker input arguments: [^go.std.net/Listener l, ^Handler handler, ^String certFile, ^String keyFile]
Joker returns: ^Error -
SetCookie
Function v1.0(SetCookie w cookie)
SetCookie adds a Set-Cookie header to the provided ResponseWriter's headers.
The provided cookie must have a valid Name. Invalid cookies may be
silently dropped.
Go input arguments: (w ResponseWriter, cookie *Cookie)
Joker input arguments: [^ResponseWriter w, ^*Cookie cookie] -
StatusText
Function v1.0(StatusText code)
StatusText returns a text for the HTTP status code. It returns the empty
string if the code is unknown.
Go input arguments: (code int)
Go returns: string
Joker input arguments: [^Int code]
Joker returns: ^String -
StripPrefix
Function v1.0(StripPrefix prefix h)
StripPrefix returns a handler that serves HTTP requests by removing the
given prefix from the request URL's Path (and RawPath if set) and invoking
the handler h. StripPrefix handles a request for a path that doesn't begin
with prefix by replying with an HTTP 404 not found error. The prefix must
match exactly: if the prefix in the request contains escaped characters
the reply is also an HTTP 404 not found error.
Go input arguments: (prefix string, h Handler)
Go returns: Handler
Joker input arguments: [^String prefix, ^Handler h]
Joker returns: ^Handler -
TimeoutHandler
Function v1.0(TimeoutHandler h dt msg)
TimeoutHandler returns a Handler that runs h with the given time limit.
The new Handler calls h.ServeHTTP to handle each request, but if a
call runs for longer than its time limit, the handler responds with
a 503 Service Unavailable error and the given message in its body.
(If msg is empty, a suitable default message will be sent.)
After such a timeout, writes by h to its ResponseWriter will return
ErrHandlerTimeout.
TimeoutHandler supports the Pusher interface but does not support
the Hijacker or Flusher interfaces.
Go input arguments: (h Handler, dt time.Duration, msg string)
Go returns: Handler
Joker input arguments: [^Handler h, ^go.std.time/Duration dt, ^String msg]
Joker returns: ^Handler
Types
-
*Client
Concrete Type v1.0A Client is an HTTP client. Its zero value (DefaultClient) is a
usable client that uses DefaultTransport.
The Client's Transport typically has internal state (cached TCP
connections), so Clients should be reused instead of created as
needed. Clients are safe for concurrent use by multiple goroutines.
A Client is higher-level than a RoundTripper (such as Transport)
and additionally handles HTTP details such as cookies and
redirects.
When following redirects, the Client will forward all headers set on the
initial Request except:
• when forwarding sensitive headers like "Authorization",
"WWW-Authenticate", and "Cookie" to untrusted targets.
These headers will be ignored when following a redirect to a domain
that is not a subdomain match or exact match of the initial domain.
For example, a redirect from "foo.com" to either "foo.com" or "sub.foo.com"
will forward the sensitive headers, but a redirect to "bar.com" will not.
• when forwarding the "Cookie" header with a non-nil cookie Jar.
Since each redirect may mutate the state of the cookie jar,
a redirect may possibly alter a cookie set in the initial request.
When forwarding the "Cookie" header, any mutated cookies will be omitted,
with the expectation that the Jar will insert those mutated cookies
with the updated values (assuming the origin matches).
If Jar is nil, the initial cookies are forwarded without change.
-
CloseIdleConnections
Receiver for *Client v1.0([])
CloseIdleConnections closes any connections on its Transport which
were previously connected from previous requests but are now
sitting idle in a "keep-alive" state. It does not interrupt any
connections currently in use.
If the Client's Transport does not have a CloseIdleConnections method
then this method does nothing.
-
Do
Receiver for *Client v1.0([req])
Do sends an HTTP request and returns an HTTP response, following
policy (such as redirects, cookies, auth) as configured on the
client.
An error is returned if caused by client policy (such as
CheckRedirect), or failure to speak HTTP (such as a network
connectivity problem). A non-2xx status code doesn't cause an
error.
If the returned error is nil, the Response will contain a non-nil
Body which the user is expected to close. If the Body is not both
read to EOF and closed, the Client's underlying RoundTripper
(typically Transport) may not be able to re-use a persistent TCP
connection to the server for a subsequent "keep-alive" request.
The request Body, if non-nil, will be closed by the underlying
Transport, even on errors.
On error, any Response can be ignored. A non-nil Response with a
non-nil error only occurs when CheckRedirect fails, and even then
the returned Response.Body is already closed.
Generally Get, Post, or PostForm will be used instead of Do.
If the server replies with a redirect, the Client first uses the
CheckRedirect function to determine whether the redirect should be
followed. If permitted, a 301, 302, or 303 redirect causes
subsequent requests to use HTTP method GET
(or HEAD if the original request was HEAD), with no body.
A 307 or 308 redirect preserves the original HTTP method and body,
provided that the Request.GetBody function is defined.
The NewRequest function automatically sets GetBody for common
standard library body types.
Any returned error will be of type *url.Error. The url.Error
value's Timeout method will report true if the request timed out.
-
Get
Receiver for *Client v1.0([url])
Get issues a GET to the specified URL. If the response is one of the
following redirect codes, Get follows the redirect after calling the
Client's CheckRedirect function:
301 (Moved Permanently)
302 (Found)
303 (See Other)
307 (Temporary Redirect)
308 (Permanent Redirect)
An error is returned if the Client's CheckRedirect function fails
or if there was an HTTP protocol error. A non-2xx response doesn't
cause an error. Any returned error will be of type *url.Error. The
url.Error value's Timeout method will report true if the request
timed out.
When err is nil, resp always contains a non-nil resp.Body.
Caller should close resp.Body when done reading from it.
To make a request with custom headers, use NewRequest and Client.Do.
To make a request with a specified context.Context, use NewRequestWithContext
and Client.Do.
-
Head
Receiver for *Client v1.0([url])
Head issues a HEAD to the specified URL. If the response is one of the
following redirect codes, Head follows the redirect after calling the
Client's CheckRedirect function:
301 (Moved Permanently)
302 (Found)
303 (See Other)
307 (Temporary Redirect)
308 (Permanent Redirect)
To make a request with a specified context.Context, use NewRequestWithContext
and Client.Do.
-
Post
Receiver for *Client v1.0([url contentType body])
Post issues a POST to the specified URL.
Caller should close resp.Body when done reading from it.
If the provided body is an io.Closer, it is closed after the
request.
To set custom headers, use NewRequest and Client.Do.
To make a request with a specified context.Context, use NewRequestWithContext
and Client.Do.
See the Client.Do method documentation for details on how redirects
are handled.
-
PostForm
Receiver for *Client v1.0([url data])
PostForm issues a POST to the specified URL,
with data's keys and values URL-encoded as the request body.
The Content-Type header is set to application/x-www-form-urlencoded.
To set other headers, use NewRequest and Client.Do.
When err is nil, resp always contains a non-nil resp.Body.
Caller should close resp.Body when done reading from it.
See the Client.Do method documentation for details on how redirects
are handled.
To make a request with a specified context.Context, use NewRequestWithContext
and Client.Do.
-
*ConnState
Concrete Type v1.0A ConnState represents the state of a client connection to a server.
It's used by the optional Server.ConnState hook.
-
*Cookie
Concrete Type v1.0A Cookie represents an HTTP cookie as sent in the Set-Cookie header of an
HTTP response or the Cookie header of an HTTP request.
See https://tools.ietf.org/html/rfc6265 for details.
-
String
Receiver for *Cookie v1.0([])
String returns the serialization of the cookie for use in a Cookie
header (if only Name and Value are set) or a Set-Cookie response
header (if other fields are set).
If c is nil or c.Name is invalid, the empty string is returned.
-
Valid
Receiver for *Cookie v1.0([])
Valid reports whether the cookie is valid.
-
*Dir
Concrete Type v1.0A Dir implements FileSystem using the native file system restricted to a
specific directory tree.
While the FileSystem.Open method takes '/'-separated paths, a Dir's string
value is a filename on the native file system, not a URL, so it is separated
by filepath.Separator, which isn't necessarily '/'.
Note that Dir could expose sensitive files and directories. Dir will follow
symlinks pointing out of the directory tree, which can be especially dangerous
if serving from a directory in which users are able to create arbitrary symlinks.
Dir will also allow access to files and directories starting with a period,
which could expose sensitive directories like .git or sensitive files like
.htpasswd. To exclude files with a leading period, remove the files/directories
from the server or create a custom FileSystem implementation.
An empty Dir is treated as ".".
-
*HandlerFunc
Concrete Type v1.0The HandlerFunc type is an adapter to allow the use of
ordinary functions as HTTP handlers. If f is a function
with the appropriate signature, HandlerFunc(f) is a
Handler that calls f.
-
*Header
Concrete Type v1.0A Header represents the key-value pairs in an HTTP header.
The keys should be in canonical form, as returned by
CanonicalHeaderKey.
-
*MaxBytesError
Concrete Type v1.0MaxBytesError is returned by MaxBytesReader when its read limit is exceeded.
-
Error
Receiver for *MaxBytesError v1.0([])
-
*ProtocolError
Concrete Type v1.0ProtocolError represents an HTTP protocol error.
Deprecated: Not all errors in the http package related to protocol errors
are of type ProtocolError.
-
Error
Receiver for *ProtocolError v1.0([])
-
*PushOptions
Concrete Type v1.0PushOptions describes options for Pusher.Push.
-
*Request
Concrete Type v1.0A Request represents an HTTP request received by a server
or to be sent by a client.
The field semantics differ slightly between client and server
usage. In addition to the notes on the fields below, see the
documentation for Request.Write and RoundTripper.
-
AddCookie
Receiver for *Request v1.0([c])
AddCookie adds a cookie to the request. Per RFC 6265 section 5.4,
AddCookie does not attach more than one Cookie header field. That
means all cookies, if any, are written into the same line,
separated by semicolon.
AddCookie only sanitizes c's name and value, and does not sanitize
a Cookie header already present in the request.
-
BasicAuth
Receiver for *Request v1.0([])
BasicAuth returns the username and password provided in the request's
Authorization header, if the request uses HTTP Basic Authentication.
See RFC 2617, Section 2.
-
Clone
Receiver for *Request v1.0([ctx])
Clone returns a deep copy of r with its context changed to ctx.
The provided ctx must be non-nil.
For an outgoing client request, the context controls the entire
lifetime of a request and its response: obtaining a connection,
sending the request, and reading the response headers and body.
-
Context
Receiver for *Request v1.0([])
Context returns the request's context. To change the context, use
WithContext.
The returned context is always non-nil; it defaults to the
background context.
For outgoing client requests, the context controls cancellation.
For incoming server requests, the context is canceled when the
client's connection closes, the request is canceled (with HTTP/2),
or when the ServeHTTP method returns.
-
Cookie
Receiver for *Request v1.0([name])
Cookie returns the named cookie provided in the request or
ErrNoCookie if not found.
If multiple cookies match the given name, only one cookie will
be returned.
-
Cookies
Receiver for *Request v1.0([])
Cookies parses and returns the HTTP cookies sent with the request.
-
FormFile
Receiver for *Request v1.0([key])
FormFile returns the first file for the provided form key.
FormFile calls ParseMultipartForm and ParseForm if necessary.
-
FormValue
Receiver for *Request v1.0([key])
FormValue returns the first value for the named component of the query.
POST and PUT body parameters take precedence over URL query string values.
FormValue calls ParseMultipartForm and ParseForm if necessary and ignores
any errors returned by these functions.
If key is not present, FormValue returns the empty string.
To access multiple values of the same key, call ParseForm and
then inspect Request.Form directly.
-
MultipartReader
Receiver for *Request v1.0([])
MultipartReader returns a MIME multipart reader if this is a
multipart/form-data or a multipart/mixed POST request, else returns nil and an error.
Use this function instead of ParseMultipartForm to
process the request body as a stream.
-
ParseForm
Receiver for *Request v1.0([])
ParseForm populates r.Form and r.PostForm.
For all requests, ParseForm parses the raw query from the URL and updates
r.Form.
For POST, PUT, and PATCH requests, it also reads the request body, parses it
as a form and puts the results into both r.PostForm and r.Form. Request body
parameters take precedence over URL query string values in r.Form.
If the request Body's size has not already been limited by MaxBytesReader,
the size is capped at 10MB.
For other HTTP methods, or when the Content-Type is not
application/x-www-form-urlencoded, the request Body is not read, and
r.PostForm is initialized to a non-nil, empty value.
ParseMultipartForm calls ParseForm automatically.
ParseForm is idempotent.
-
ParseMultipartForm
Receiver for *Request v1.0([maxMemory])
ParseMultipartForm parses a request body as multipart/form-data.
The whole request body is parsed and up to a total of maxMemory bytes of
its file parts are stored in memory, with the remainder stored on
disk in temporary files.
ParseMultipartForm calls ParseForm if necessary.
If ParseForm returns an error, ParseMultipartForm returns it but also
continues parsing the request body.
After one call to ParseMultipartForm, subsequent calls have no effect.
-
PostFormValue
Receiver for *Request v1.0([key])
PostFormValue returns the first value for the named component of the POST,
PATCH, or PUT request body. URL query parameters are ignored.
PostFormValue calls ParseMultipartForm and ParseForm if necessary and ignores
any errors returned by these functions.
If key is not present, PostFormValue returns the empty string.
-
ProtoAtLeast
Receiver for *Request v1.0([major minor])
ProtoAtLeast reports whether the HTTP protocol used
in the request is at least major.minor.
-
Referer
Receiver for *Request v1.0([])
Referer returns the referring URL, if sent in the request.
Referer is misspelled as in the request itself, a mistake from the
earliest days of HTTP. This value can also be fetched from the
Header map as Header["Referer"]; the benefit of making it available
as a method is that the compiler can diagnose programs that use the
alternate (correct English) spelling req.Referrer() but cannot
diagnose programs that use Header["Referrer"].
-
SetBasicAuth
Receiver for *Request v1.0([username password])
SetBasicAuth sets the request's Authorization header to use HTTP
Basic Authentication with the provided username and password.
With HTTP Basic Authentication the provided username and password
are not encrypted. It should generally only be used in an HTTPS
request.
The username may not contain a colon. Some protocols may impose
additional requirements on pre-escaping the username and
password. For instance, when used with OAuth2, both arguments must
be URL encoded first with url.QueryEscape.
-
UserAgent
Receiver for *Request v1.0([])
UserAgent returns the client's User-Agent, if sent in the request.
-
WithContext
Receiver for *Request v1.0([ctx])
WithContext returns a shallow copy of r with its context changed
to ctx. The provided ctx must be non-nil.
For outgoing client request, the context controls the entire
lifetime of a request and its response: obtaining a connection,
sending the request, and reading the response headers and body.
To create a new request with a context, use NewRequestWithContext.
To change the context of a request, such as an incoming request you
want to modify before sending back out, use Request.Clone. Between
those two uses, it's rare to need WithContext.
-
Write
Receiver for *Request v1.0([w])
Write writes an HTTP/1.1 request, which is the header and body, in wire format.
This method consults the following fields of the request:
Host
URL
Method (defaults to "GET")
Header
ContentLength
TransferEncoding
Body
If Body is present, Content-Length is <= 0 and TransferEncoding
hasn't been set to "identity", Write adds "Transfer-Encoding:
chunked" to the header. Body is closed after it is sent.
-
WriteProxy
Receiver for *Request v1.0([w])
WriteProxy is like Write but writes the request in the form
expected by an HTTP proxy. In particular, WriteProxy writes the
initial Request-URI line of the request with an absolute URI, per
section 5.3 of RFC 7230, including the scheme and host.
In either case, WriteProxy also writes a Host header, using
either r.Host or r.URL.Host.
-
*Response
Concrete Type v1.0Response represents the response from an HTTP request.
The Client and Transport return Responses from servers once
the response headers have been received. The response body
is streamed on demand as the Body field is read.
-
Cookies
Receiver for *Response v1.0([])
Cookies parses and returns the cookies set in the Set-Cookie headers.
-
Location
Receiver for *Response v1.0([])
Location returns the URL of the response's "Location" header,
if present. Relative redirects are resolved relative to
the Response's Request. ErrNoLocation is returned if no
Location header is present.
-
ProtoAtLeast
Receiver for *Response v1.0([major minor])
ProtoAtLeast reports whether the HTTP protocol used
in the response is at least major.minor.
-
Write
Receiver for *Response v1.0([w])
Write writes r to w in the HTTP/1.x server response format,
including the status line, headers, body, and optional trailer.
This method consults the following fields of the response r:
StatusCode
ProtoMajor
ProtoMinor
Request.Method
TransferEncoding
Trailer
Body
ContentLength
Header, values for non-canonical keys will have unpredictable behavior
The Response Body is closed after it is sent.
-
*SameSite
Concrete Type v1.0SameSite allows a server to define a cookie attribute making it impossible for
the browser to send this cookie along with cross-site requests. The main
goal is to mitigate the risk of cross-origin information leakage, and provide
some protection against cross-site request forgery attacks.
See https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00 for details.
-
*ServeMux
Concrete Type v1.0ServeMux is an HTTP request multiplexer.
It matches the URL of each incoming request against a list of registered
patterns and calls the handler for the pattern that
most closely matches the URL.
Patterns name fixed, rooted paths, like "/favicon.ico",
or rooted subtrees, like "/images/" (note the trailing slash).
Longer patterns take precedence over shorter ones, so that
if there are handlers registered for both "/images/"
and "/images/thumbnails/", the latter handler will be
called for paths beginning "/images/thumbnails/" and the
former will receive requests for any other paths in the
"/images/" subtree.
Note that since a pattern ending in a slash names a rooted subtree,
the pattern "/" matches all paths not matched by other registered
patterns, not just the URL with Path == "/".
If a subtree has been registered and a request is received naming the
subtree root without its trailing slash, ServeMux redirects that
request to the subtree root (adding the trailing slash). This behavior can
be overridden with a separate registration for the path without
the trailing slash. For example, registering "/images/" causes ServeMux
to redirect a request for "/images" to "/images/", unless "/images" has
been registered separately.
Patterns may optionally begin with a host name, restricting matches to
URLs on that host only. Host-specific patterns take precedence over
general patterns, so that a handler might register for the two patterns
"/codesearch" and "codesearch.google.com/" without also taking over
requests for "http://www.google.com/".
ServeMux also takes care of sanitizing the URL request path and the Host
header, stripping the port number and redirecting any request containing . or
.. elements or repeated slashes to an equivalent, cleaner URL.
-
Handle
Receiver for *ServeMux v1.0([pattern handler])
Handle registers the handler for the given pattern.
If a handler already exists for pattern, Handle panics.
-
Handler
Receiver for *ServeMux v1.0([r])
Handler returns the handler to use for the given request,
consulting r.Method, r.Host, and r.URL.Path. It always returns
a non-nil handler. If the path is not in its canonical form, the
handler will be an internally-generated handler that redirects
to the canonical path. If the host contains a port, it is ignored
when matching handlers.
The path and host are used unchanged for CONNECT requests.
Handler also returns the registered pattern that matches the
request or, in the case of internally-generated redirects,
the pattern that will match after following the redirect.
If there is no registered handler that applies to the request,
Handler returns a “page not found” handler and an empty pattern.
-
ServeHTTP
Receiver for *ServeMux v1.0([w r])
ServeHTTP dispatches the request to the handler whose
pattern most closely matches the request URL.
-
*Server
Concrete Type v1.0A Server defines parameters for running an HTTP server.
The zero value for Server is a valid configuration.
-
Close
Receiver for *Server v1.0([])
Close immediately closes all active net.Listeners and any
connections in state StateNew, StateActive, or StateIdle. For a
graceful shutdown, use Shutdown.
Close does not attempt to close (and does not even know about)
any hijacked connections, such as WebSockets.
Close returns any error returned from closing the Server's
underlying Listener(s).
-
ListenAndServe
Receiver for *Server v1.0([])
ListenAndServe listens on the TCP network address srv.Addr and then
calls Serve to handle requests on incoming connections.
Accepted connections are configured to enable TCP keep-alives.
If srv.Addr is blank, ":http" is used.
ListenAndServe always returns a non-nil error. After Shutdown or Close,
the returned error is ErrServerClosed.
-
ListenAndServeTLS
Receiver for *Server v1.0([certFile keyFile])
ListenAndServeTLS listens on the TCP network address srv.Addr and
then calls ServeTLS to handle requests on incoming TLS connections.
Accepted connections are configured to enable TCP keep-alives.
Filenames containing a certificate and matching private key for the
server must be provided if neither the Server's TLSConfig.Certificates
nor TLSConfig.GetCertificate are populated. If the certificate is
signed by a certificate authority, the certFile should be the
concatenation of the server's certificate, any intermediates, and
the CA's certificate.
If srv.Addr is blank, ":https" is used.
ListenAndServeTLS always returns a non-nil error. After Shutdown or
Close, the returned error is ErrServerClosed.
-
RegisterOnShutdown
Receiver for *Server v1.0([f])
RegisterOnShutdown registers a function to call on Shutdown.
This can be used to gracefully shutdown connections that have
undergone ALPN protocol upgrade or that have been hijacked.
This function should start protocol-specific graceful shutdown,
but should not wait for shutdown to complete.
-
Serve
Receiver for *Server v1.0([l])
Serve accepts incoming connections on the Listener l, creating a
new service goroutine for each. The service goroutines read requests and
then call srv.Handler to reply to them.
HTTP/2 support is only enabled if the Listener returns *tls.Conn
connections and they were configured with "h2" in the TLS
Config.NextProtos.
Serve always returns a non-nil error and closes l.
After Shutdown or Close, the returned error is ErrServerClosed.
-
ServeTLS
Receiver for *Server v1.0([l certFile keyFile])
ServeTLS accepts incoming connections on the Listener l, creating a
new service goroutine for each. The service goroutines perform TLS
setup and then read requests, calling srv.Handler to reply to them.
Files containing a certificate and matching private key for the
server must be provided if neither the Server's
TLSConfig.Certificates nor TLSConfig.GetCertificate are populated.
If the certificate is signed by a certificate authority, the
certFile should be the concatenation of the server's certificate,
any intermediates, and the CA's certificate.
ServeTLS always returns a non-nil error. After Shutdown or Close, the
returned error is ErrServerClosed.
-
SetKeepAlivesEnabled
Receiver for *Server v1.0([v])
SetKeepAlivesEnabled controls whether HTTP keep-alives are enabled.
By default, keep-alives are always enabled. Only very
resource-constrained environments or servers in the process of
shutting down should disable them.
-
Shutdown
Receiver for *Server v1.0([ctx])
Shutdown gracefully shuts down the server without interrupting any
active connections. Shutdown works by first closing all open
listeners, then closing all idle connections, and then waiting
indefinitely for connections to return to idle and then shut down.
If the provided context expires before the shutdown is complete,
Shutdown returns the context's error, otherwise it returns any
error returned from closing the Server's underlying Listener(s).
When Shutdown is called, Serve, ListenAndServe, and
ListenAndServeTLS immediately return ErrServerClosed. Make sure the
program doesn't exit and waits instead for Shutdown to return.
Shutdown does not attempt to close nor wait for hijacked
connections such as WebSockets. The caller of Shutdown should
separately notify such long-lived connections of shutdown and wait
for them to close, if desired. See RegisterOnShutdown for a way to
register shutdown notification functions.
Once Shutdown has been called on a server, it may not be reused;
future calls to methods such as Serve will return ErrServerClosed.
-
*Transport
Concrete Type v1.0Transport is an implementation of RoundTripper that supports HTTP,
HTTPS, and HTTP proxies (for either HTTP or HTTPS with CONNECT).
By default, Transport caches connections for future re-use.
This may leave many open connections when accessing many hosts.
This behavior can be managed using Transport's CloseIdleConnections method
and the MaxIdleConnsPerHost and DisableKeepAlives fields.
Transports should be reused instead of created as needed.
Transports are safe for concurrent use by multiple goroutines.
A Transport is a low-level primitive for making HTTP and HTTPS requests.
For high-level functionality, such as cookies and redirects, see Client.
Transport uses HTTP/1.1 for HTTP URLs and either HTTP/1.1 or HTTP/2
for HTTPS URLs, depending on whether the server supports HTTP/2,
and how the Transport is configured. The DefaultTransport supports HTTP/2.
To explicitly enable HTTP/2 on a transport, use golang.org/x/net/http2
and call ConfigureTransport. See the package docs for more about HTTP/2.
Responses with status codes in the 1xx range are either handled
automatically (100 expect-continue) or ignored. The one
exception is HTTP status code 101 (Switching Protocols), which is
considered a terminal status and returned by RoundTrip. To see the
ignored 1xx responses, use the httptrace trace package's
ClientTrace.Got1xxResponse.
Transport only retries a request upon encountering a network error
if the request is idempotent and either has no body or has its
Request.GetBody defined. HTTP requests are considered idempotent if
they have HTTP methods GET, HEAD, OPTIONS, or TRACE; or if their
Header map contains an "Idempotency-Key" or "X-Idempotency-Key"
entry. If the idempotency key value is a zero-length slice, the
request is treated as idempotent but the header is not sent on the
wire.
-
CancelRequest
Receiver for *Transport v1.0([req])
CancelRequest cancels an in-flight request by closing its connection.
CancelRequest should only be called after RoundTrip has returned.
Deprecated: Use Request.WithContext to create a request with a
cancelable context instead. CancelRequest cannot cancel HTTP/2
requests.
-
Clone
Receiver for *Transport v1.0([])
Clone returns a deep copy of t's exported fields.
-
CloseIdleConnections
Receiver for *Transport v1.0([])
CloseIdleConnections closes any connections which were previously
connected from previous requests but are now sitting idle in
a "keep-alive" state. It does not interrupt any connections currently
in use.
-
RegisterProtocol
Receiver for *Transport v1.0([scheme rt])
RegisterProtocol registers a new protocol with scheme.
The Transport will pass requests using the given scheme to rt.
It is rt's responsibility to simulate HTTP request semantics.
RegisterProtocol can be used by other packages to provide
implementations of protocol schemes like "ftp" or "file".
If rt.RoundTrip returns ErrSkipAltProtocol, the Transport will
handle the RoundTrip itself for that one request, as if the
protocol were not registered.
-
RoundTrip
Receiver for *Transport v1.0([req])
RoundTrip implements the RoundTripper interface.
For higher-level HTTP client support (such as handling of cookies
and redirects), see Get, Post, and the Client type.
Like the RoundTripper interface, the error types returned
by RoundTrip are unspecified.
-
Client
Concrete Type v1.0A Client is an HTTP client. Its zero value (DefaultClient) is a
usable client that uses DefaultTransport.
The Client's Transport typically has internal state (cached TCP
connections), so Clients should be reused instead of created as
needed. Clients are safe for concurrent use by multiple goroutines.
A Client is higher-level than a RoundTripper (such as Transport)
and additionally handles HTTP details such as cookies and
redirects.
When following redirects, the Client will forward all headers set on the
initial Request except:
• when forwarding sensitive headers like "Authorization",
"WWW-Authenticate", and "Cookie" to untrusted targets.
These headers will be ignored when following a redirect to a domain
that is not a subdomain match or exact match of the initial domain.
For example, a redirect from "foo.com" to either "foo.com" or "sub.foo.com"
will forward the sensitive headers, but a redirect to "bar.com" will not.
• when forwarding the "Cookie" header with a non-nil cookie Jar.
Since each redirect may mutate the state of the cookie jar,
a redirect may possibly alter a cookie set in the initial request.
When forwarding the "Cookie" header, any mutated cookies will be omitted,
with the expectation that the Jar will insert those mutated cookies
with the updated values (assuming the origin matches).
If Jar is nil, the initial cookies are forwarded without change.
-
CloseNotifier
Abstract Type v1.0The CloseNotifier interface is implemented by ResponseWriters which
allow detecting when the underlying connection has gone away.
This mechanism can be used to cancel long operations on the server
if the client has disconnected before the response is ready.
Deprecated: the CloseNotifier interface predates Go's context package.
New code should use Request.Context instead.
-
CloseNotify
Method for CloseNotifier v1.0([])
-
ConnState
Concrete Type v1.0A ConnState represents the state of a client connection to a server.
It's used by the optional Server.ConnState hook.
-
String
Receiver for ConnState v1.0([])
-
Cookie
Concrete Type v1.0A Cookie represents an HTTP cookie as sent in the Set-Cookie header of an
HTTP response or the Cookie header of an HTTP request.
See https://tools.ietf.org/html/rfc6265 for details.
-
CookieJar
Abstract Type v1.0A CookieJar manages storage and use of cookies in HTTP requests.
Implementations of CookieJar must be safe for concurrent use by multiple
goroutines.
The net/http/cookiejar package provides a CookieJar implementation.
-
Cookies
Method for CookieJar v1.0([u])
-
SetCookies
Method for CookieJar v1.0([u cookies])
-
Dir
Concrete Type v1.0A Dir implements FileSystem using the native file system restricted to a
specific directory tree.
While the FileSystem.Open method takes '/'-separated paths, a Dir's string
value is a filename on the native file system, not a URL, so it is separated
by filepath.Separator, which isn't necessarily '/'.
Note that Dir could expose sensitive files and directories. Dir will follow
symlinks pointing out of the directory tree, which can be especially dangerous
if serving from a directory in which users are able to create arbitrary symlinks.
Dir will also allow access to files and directories starting with a period,
which could expose sensitive directories like .git or sensitive files like
.htpasswd. To exclude files with a leading period, remove the files/directories
from the server or create a custom FileSystem implementation.
An empty Dir is treated as ".".
-
Open
Receiver for Dir v1.0([name])
Open implements FileSystem using os.Open, opening files for reading rooted
and relative to the directory d.
-
File
Abstract Type v1.0A File is returned by a FileSystem's Open method and can be
served by the FileServer implementation.
The methods should behave the same as those on an *os.File.
-
Close
Method for File v1.0([])
-
Read
Method for File v1.0([p])
-
Readdir
Method for File v1.0([count])
-
Seek
Method for File v1.0([offset whence])
-
Stat
Method for File v1.0([])
-
FileSystem
Abstract Type v1.0A FileSystem implements access to a collection of named files.
The elements in a file path are separated by slash ('/', U+002F)
characters, regardless of host operating system convention.
See the FileServer function to convert a FileSystem to a Handler.
This interface predates the fs.FS interface, which can be used instead:
the FS adapter function converts an fs.FS to a FileSystem.
-
Open
Method for FileSystem v1.0([name])
-
Flusher
Abstract Type v1.0The Flusher interface is implemented by ResponseWriters that allow
an HTTP handler to flush buffered data to the client.
The default HTTP/1.x and HTTP/2 ResponseWriter implementations
support Flusher, but ResponseWriter wrappers may not. Handlers
should always test for this ability at runtime.
Note that even for ResponseWriters that support Flush,
if the client is connected through an HTTP proxy,
the buffered data may not reach the client until the response
completes.
-
Flush
Method for Flusher v1.0([])
-
Handler
Abstract Type v1.0A Handler responds to an HTTP request.
ServeHTTP should write reply headers and data to the ResponseWriter
and then return. Returning signals that the request is finished; it
is not valid to use the ResponseWriter or read from the
Request.Body after or concurrently with the completion of the
ServeHTTP call.
Depending on the HTTP client software, HTTP protocol version, and
any intermediaries between the client and the Go server, it may not
be possible to read from the Request.Body after writing to the
ResponseWriter. Cautious handlers should read the Request.Body
first, and then reply.
Except for reading the body, handlers should not modify the
provided Request.
If ServeHTTP panics, the server (the caller of ServeHTTP) assumes
that the effect of the panic was isolated to the active request.
It recovers the panic, logs a stack trace to the server error log,
and either closes the network connection or sends an HTTP/2
RST_STREAM, depending on the HTTP protocol. To abort a handler so
the client sees an interrupted response but the server doesn't log
an error, panic with the value ErrAbortHandler.
-
ServeHTTP
Method for Handler v1.0([arg1 arg2])
-
HandlerFunc
Concrete Type v1.0The HandlerFunc type is an adapter to allow the use of
ordinary functions as HTTP handlers. If f is a function
with the appropriate signature, HandlerFunc(f) is a
Handler that calls f.
-
ServeHTTP
Receiver for HandlerFunc v1.0([w r])
ServeHTTP calls f(w, r).
-
Header
Concrete Type v1.0A Header represents the key-value pairs in an HTTP header.
The keys should be in canonical form, as returned by
CanonicalHeaderKey.
-
Add
Receiver for Header v1.0([key value])
Add adds the key, value pair to the header.
It appends to any existing values associated with key.
The key is case insensitive; it is canonicalized by
CanonicalHeaderKey.
-
Clone
Receiver for Header v1.0([])
Clone returns a copy of h or nil if h is nil.
-
Del
Receiver for Header v1.0([key])
Del deletes the values associated with key.
The key is case insensitive; it is canonicalized by
CanonicalHeaderKey.
-
Get
Receiver for Header v1.0([key])
Get gets the first value associated with the given key. If
there are no values associated with the key, Get returns "".
It is case insensitive; textproto.CanonicalMIMEHeaderKey is
used to canonicalize the provided key. Get assumes that all
keys are stored in canonical form. To use non-canonical keys,
access the map directly.
-
Set
Receiver for Header v1.0([key value])
Set sets the header entries associated with key to the
single element value. It replaces any existing values
associated with key. The key is case insensitive; it is
canonicalized by textproto.CanonicalMIMEHeaderKey.
To use non-canonical keys, assign to the map directly.
-
Values
Receiver for Header v1.0([key])
Values returns all values associated with the given key.
It is case insensitive; textproto.CanonicalMIMEHeaderKey is
used to canonicalize the provided key. To use non-canonical
keys, access the map directly.
The returned slice is not a copy.
-
Write
Receiver for Header v1.0([w])
Write writes a header in wire format.
-
Hijacker
Abstract Type v1.0The Hijacker interface is implemented by ResponseWriters that allow
an HTTP handler to take over the connection.
The default ResponseWriter for HTTP/1.x connections supports
Hijacker, but HTTP/2 connections intentionally do not.
ResponseWriter wrappers may also not support Hijacker. Handlers
should always test for this ability at runtime.
-
Hijack
Method for Hijacker v1.0([])
-
MaxBytesError
Concrete Type v1.0MaxBytesError is returned by MaxBytesReader when its read limit is exceeded.
-
ProtocolError
Concrete Type v1.0ProtocolError represents an HTTP protocol error.
Deprecated: Not all errors in the http package related to protocol errors
are of type ProtocolError.
-
PushOptions
Concrete Type v1.0PushOptions describes options for Pusher.Push.
-
Pusher
Abstract Type v1.0Pusher is the interface implemented by ResponseWriters that support
HTTP/2 server push. For more background, see
https://tools.ietf.org/html/rfc7540#section-8.2.
-
Push
Method for Pusher v1.0([target opts])
-
Request
Concrete Type v1.0A Request represents an HTTP request received by a server
or to be sent by a client.
The field semantics differ slightly between client and server
usage. In addition to the notes on the fields below, see the
documentation for Request.Write and RoundTripper.
-
Response
Concrete Type v1.0Response represents the response from an HTTP request.
The Client and Transport return Responses from servers once
the response headers have been received. The response body
is streamed on demand as the Body field is read.
-
ResponseWriter
Abstract Type v1.0A ResponseWriter interface is used by an HTTP handler to
construct an HTTP response.
A ResponseWriter may not be used after the Handler.ServeHTTP method
has returned.
-
Header
Method for ResponseWriter v1.0([])
-
Write
Method for ResponseWriter v1.0([arg1])
-
WriteHeader
Method for ResponseWriter v1.0([statusCode])
-
RoundTripper
Abstract Type v1.0RoundTripper is an interface representing the ability to execute a
single HTTP transaction, obtaining the Response for a given Request.
A RoundTripper must be safe for concurrent use by multiple
goroutines.
-
RoundTrip
Method for RoundTripper v1.0([arg1])
-
SameSite
Concrete Type v1.0SameSite allows a server to define a cookie attribute making it impossible for
the browser to send this cookie along with cross-site requests. The main
goal is to mitigate the risk of cross-origin information leakage, and provide
some protection against cross-site request forgery attacks.
See https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00 for details.
-
ServeMux
Concrete Type v1.0ServeMux is an HTTP request multiplexer.
It matches the URL of each incoming request against a list of registered
patterns and calls the handler for the pattern that
most closely matches the URL.
Patterns name fixed, rooted paths, like "/favicon.ico",
or rooted subtrees, like "/images/" (note the trailing slash).
Longer patterns take precedence over shorter ones, so that
if there are handlers registered for both "/images/"
and "/images/thumbnails/", the latter handler will be
called for paths beginning "/images/thumbnails/" and the
former will receive requests for any other paths in the
"/images/" subtree.
Note that since a pattern ending in a slash names a rooted subtree,
the pattern "/" matches all paths not matched by other registered
patterns, not just the URL with Path == "/".
If a subtree has been registered and a request is received naming the
subtree root without its trailing slash, ServeMux redirects that
request to the subtree root (adding the trailing slash). This behavior can
be overridden with a separate registration for the path without
the trailing slash. For example, registering "/images/" causes ServeMux
to redirect a request for "/images" to "/images/", unless "/images" has
been registered separately.
Patterns may optionally begin with a host name, restricting matches to
URLs on that host only. Host-specific patterns take precedence over
general patterns, so that a handler might register for the two patterns
"/codesearch" and "codesearch.google.com/" without also taking over
requests for "http://www.google.com/".
ServeMux also takes care of sanitizing the URL request path and the Host
header, stripping the port number and redirecting any request containing . or
.. elements or repeated slashes to an equivalent, cleaner URL.
-
Server
Concrete Type v1.0A Server defines parameters for running an HTTP server.
The zero value for Server is a valid configuration.
-
Transport
Concrete Type v1.0Transport is an implementation of RoundTripper that supports HTTP,
HTTPS, and HTTP proxies (for either HTTP or HTTPS with CONNECT).
By default, Transport caches connections for future re-use.
This may leave many open connections when accessing many hosts.
This behavior can be managed using Transport's CloseIdleConnections method
and the MaxIdleConnsPerHost and DisableKeepAlives fields.
Transports should be reused instead of created as needed.
Transports are safe for concurrent use by multiple goroutines.
A Transport is a low-level primitive for making HTTP and HTTPS requests.
For high-level functionality, such as cookies and redirects, see Client.
Transport uses HTTP/1.1 for HTTP URLs and either HTTP/1.1 or HTTP/2
for HTTPS URLs, depending on whether the server supports HTTP/2,
and how the Transport is configured. The DefaultTransport supports HTTP/2.
To explicitly enable HTTP/2 on a transport, use golang.org/x/net/http2
and call ConfigureTransport. See the package docs for more about HTTP/2.
Responses with status codes in the 1xx range are either handled
automatically (100 expect-continue) or ignored. The one
exception is HTTP status code 101 (Switching Protocols), which is
considered a terminal status and returned by RoundTrip. To see the
ignored 1xx responses, use the httptrace trace package's
ClientTrace.Got1xxResponse.
Transport only retries a request upon encountering a network error
if the request is idempotent and either has no body or has its
Request.GetBody defined. HTTP requests are considered idempotent if
they have HTTP methods GET, HEAD, OPTIONS, or TRACE; or if their
Header map contains an "Idempotency-Key" or "X-Idempotency-Key"
entry. If the idempotency key value is a zero-length slice, the
request is treated as idempotent but the header is not sent on the
wire.
-
arrayOfClient
Concrete Type v1.0A Client is an HTTP client. Its zero value (DefaultClient) is a
usable client that uses DefaultTransport.
The Client's Transport typically has internal state (cached TCP
connections), so Clients should be reused instead of created as
needed. Clients are safe for concurrent use by multiple goroutines.
A Client is higher-level than a RoundTripper (such as Transport)
and additionally handles HTTP details such as cookies and
redirects.
When following redirects, the Client will forward all headers set on the
initial Request except:
• when forwarding sensitive headers like "Authorization",
"WWW-Authenticate", and "Cookie" to untrusted targets.
These headers will be ignored when following a redirect to a domain
that is not a subdomain match or exact match of the initial domain.
For example, a redirect from "foo.com" to either "foo.com" or "sub.foo.com"
will forward the sensitive headers, but a redirect to "bar.com" will not.
• when forwarding the "Cookie" header with a non-nil cookie Jar.
Since each redirect may mutate the state of the cookie jar,
a redirect may possibly alter a cookie set in the initial request.
When forwarding the "Cookie" header, any mutated cookies will be omitted,
with the expectation that the Jar will insert those mutated cookies
with the updated values (assuming the origin matches).
If Jar is nil, the initial cookies are forwarded without change.
-
arrayOfCloseNotifier
Concrete Type v1.0The CloseNotifier interface is implemented by ResponseWriters which
allow detecting when the underlying connection has gone away.
This mechanism can be used to cancel long operations on the server
if the client has disconnected before the response is ready.
Deprecated: the CloseNotifier interface predates Go's context package.
New code should use Request.Context instead.
-
arrayOfConnState
Concrete Type v1.0A ConnState represents the state of a client connection to a server.
It's used by the optional Server.ConnState hook.
-
arrayOfCookie
Concrete Type v1.0A Cookie represents an HTTP cookie as sent in the Set-Cookie header of an
HTTP response or the Cookie header of an HTTP request.
See https://tools.ietf.org/html/rfc6265 for details.
-
arrayOfCookieJar
Concrete Type v1.0A CookieJar manages storage and use of cookies in HTTP requests.
Implementations of CookieJar must be safe for concurrent use by multiple
goroutines.
The net/http/cookiejar package provides a CookieJar implementation.
-
arrayOfDir
Concrete Type v1.0A Dir implements FileSystem using the native file system restricted to a
specific directory tree.
While the FileSystem.Open method takes '/'-separated paths, a Dir's string
value is a filename on the native file system, not a URL, so it is separated
by filepath.Separator, which isn't necessarily '/'.
Note that Dir could expose sensitive files and directories. Dir will follow
symlinks pointing out of the directory tree, which can be especially dangerous
if serving from a directory in which users are able to create arbitrary symlinks.
Dir will also allow access to files and directories starting with a period,
which could expose sensitive directories like .git or sensitive files like
.htpasswd. To exclude files with a leading period, remove the files/directories
from the server or create a custom FileSystem implementation.
An empty Dir is treated as ".".
-
arrayOfFile
Concrete Type v1.0A File is returned by a FileSystem's Open method and can be
served by the FileServer implementation.
The methods should behave the same as those on an *os.File.
-
arrayOfFileSystem
Concrete Type v1.0A FileSystem implements access to a collection of named files.
The elements in a file path are separated by slash ('/', U+002F)
characters, regardless of host operating system convention.
See the FileServer function to convert a FileSystem to a Handler.
This interface predates the fs.FS interface, which can be used instead:
the FS adapter function converts an fs.FS to a FileSystem.
-
arrayOfFlusher
Concrete Type v1.0The Flusher interface is implemented by ResponseWriters that allow
an HTTP handler to flush buffered data to the client.
The default HTTP/1.x and HTTP/2 ResponseWriter implementations
support Flusher, but ResponseWriter wrappers may not. Handlers
should always test for this ability at runtime.
Note that even for ResponseWriters that support Flush,
if the client is connected through an HTTP proxy,
the buffered data may not reach the client until the response
completes.
-
arrayOfHandler
Concrete Type v1.0A Handler responds to an HTTP request.
ServeHTTP should write reply headers and data to the ResponseWriter
and then return. Returning signals that the request is finished; it
is not valid to use the ResponseWriter or read from the
Request.Body after or concurrently with the completion of the
ServeHTTP call.
Depending on the HTTP client software, HTTP protocol version, and
any intermediaries between the client and the Go server, it may not
be possible to read from the Request.Body after writing to the
ResponseWriter. Cautious handlers should read the Request.Body
first, and then reply.
Except for reading the body, handlers should not modify the
provided Request.
If ServeHTTP panics, the server (the caller of ServeHTTP) assumes
that the effect of the panic was isolated to the active request.
It recovers the panic, logs a stack trace to the server error log,
and either closes the network connection or sends an HTTP/2
RST_STREAM, depending on the HTTP protocol. To abort a handler so
the client sees an interrupted response but the server doesn't log
an error, panic with the value ErrAbortHandler.
-
arrayOfHandlerFunc
Concrete Type v1.0The HandlerFunc type is an adapter to allow the use of
ordinary functions as HTTP handlers. If f is a function
with the appropriate signature, HandlerFunc(f) is a
Handler that calls f.
-
arrayOfHeader
Concrete Type v1.0A Header represents the key-value pairs in an HTTP header.
The keys should be in canonical form, as returned by
CanonicalHeaderKey.
-
arrayOfHijacker
Concrete Type v1.0The Hijacker interface is implemented by ResponseWriters that allow
an HTTP handler to take over the connection.
The default ResponseWriter for HTTP/1.x connections supports
Hijacker, but HTTP/2 connections intentionally do not.
ResponseWriter wrappers may also not support Hijacker. Handlers
should always test for this ability at runtime.
-
arrayOfMaxBytesError
Concrete Type v1.0MaxBytesError is returned by MaxBytesReader when its read limit is exceeded.
-
arrayOfProtocolError
Concrete Type v1.0ProtocolError represents an HTTP protocol error.
Deprecated: Not all errors in the http package related to protocol errors
are of type ProtocolError.
-
arrayOfPushOptions
Concrete Type v1.0PushOptions describes options for Pusher.Push.
-
arrayOfPusher
Concrete Type v1.0Pusher is the interface implemented by ResponseWriters that support
HTTP/2 server push. For more background, see
https://tools.ietf.org/html/rfc7540#section-8.2.
-
arrayOfRequest
Concrete Type v1.0A Request represents an HTTP request received by a server
or to be sent by a client.
The field semantics differ slightly between client and server
usage. In addition to the notes on the fields below, see the
documentation for Request.Write and RoundTripper.
-
arrayOfResponse
Concrete Type v1.0Response represents the response from an HTTP request.
The Client and Transport return Responses from servers once
the response headers have been received. The response body
is streamed on demand as the Body field is read.
-
arrayOfResponseWriter
Concrete Type v1.0A ResponseWriter interface is used by an HTTP handler to
construct an HTTP response.
A ResponseWriter may not be used after the Handler.ServeHTTP method
has returned.
-
arrayOfRoundTripper
Concrete Type v1.0RoundTripper is an interface representing the ability to execute a
single HTTP transaction, obtaining the Response for a given Request.
A RoundTripper must be safe for concurrent use by multiple
goroutines.
-
arrayOfSameSite
Concrete Type v1.0SameSite allows a server to define a cookie attribute making it impossible for
the browser to send this cookie along with cross-site requests. The main
goal is to mitigate the risk of cross-origin information leakage, and provide
some protection against cross-site request forgery attacks.
See https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00 for details.
-
arrayOfServeMux
Concrete Type v1.0ServeMux is an HTTP request multiplexer.
It matches the URL of each incoming request against a list of registered
patterns and calls the handler for the pattern that
most closely matches the URL.
Patterns name fixed, rooted paths, like "/favicon.ico",
or rooted subtrees, like "/images/" (note the trailing slash).
Longer patterns take precedence over shorter ones, so that
if there are handlers registered for both "/images/"
and "/images/thumbnails/", the latter handler will be
called for paths beginning "/images/thumbnails/" and the
former will receive requests for any other paths in the
"/images/" subtree.
Note that since a pattern ending in a slash names a rooted subtree,
the pattern "/" matches all paths not matched by other registered
patterns, not just the URL with Path == "/".
If a subtree has been registered and a request is received naming the
subtree root without its trailing slash, ServeMux redirects that
request to the subtree root (adding the trailing slash). This behavior can
be overridden with a separate registration for the path without
the trailing slash. For example, registering "/images/" causes ServeMux
to redirect a request for "/images" to "/images/", unless "/images" has
been registered separately.
Patterns may optionally begin with a host name, restricting matches to
URLs on that host only. Host-specific patterns take precedence over
general patterns, so that a handler might register for the two patterns
"/codesearch" and "codesearch.google.com/" without also taking over
requests for "http://www.google.com/".
ServeMux also takes care of sanitizing the URL request path and the Host
header, stripping the port number and redirecting any request containing . or
.. elements or repeated slashes to an equivalent, cleaner URL.
-
arrayOfServer
Concrete Type v1.0A Server defines parameters for running an HTTP server.
The zero value for Server is a valid configuration.
-
arrayOfTransport
Concrete Type v1.0Transport is an implementation of RoundTripper that supports HTTP,
HTTPS, and HTTP proxies (for either HTTP or HTTPS with CONNECT).
By default, Transport caches connections for future re-use.
This may leave many open connections when accessing many hosts.
This behavior can be managed using Transport's CloseIdleConnections method
and the MaxIdleConnsPerHost and DisableKeepAlives fields.
Transports should be reused instead of created as needed.
Transports are safe for concurrent use by multiple goroutines.
A Transport is a low-level primitive for making HTTP and HTTPS requests.
For high-level functionality, such as cookies and redirects, see Client.
Transport uses HTTP/1.1 for HTTP URLs and either HTTP/1.1 or HTTP/2
for HTTPS URLs, depending on whether the server supports HTTP/2,
and how the Transport is configured. The DefaultTransport supports HTTP/2.
To explicitly enable HTTP/2 on a transport, use golang.org/x/net/http2
and call ConfigureTransport. See the package docs for more about HTTP/2.
Responses with status codes in the 1xx range are either handled
automatically (100 expect-continue) or ignored. The one
exception is HTTP status code 101 (Switching Protocols), which is
considered a terminal status and returned by RoundTrip. To see the
ignored 1xx responses, use the httptrace trace package's
ClientTrace.Got1xxResponse.
Transport only retries a request upon encountering a network error
if the request is idempotent and either has no body or has its
Request.GetBody defined. HTTP requests are considered idempotent if
they have HTTP methods GET, HEAD, OPTIONS, or TRACE; or if their
Header map contains an "Idempotency-Key" or "X-Idempotency-Key"
entry. If the idempotency key value is a zero-length slice, the
request is treated as idempotent but the header is not sent on the
wire.