2021-04-18 15:41:13 -04:00
|
|
|
// Copyright (c) 2015-2021 MinIO, Inc.
|
|
|
|
//
|
|
|
|
// This file is part of MinIO Object Storage stack
|
|
|
|
//
|
|
|
|
// This program is free software: you can redistribute it and/or modify
|
|
|
|
// it under the terms of the GNU Affero General Public License as published by
|
|
|
|
// the Free Software Foundation, either version 3 of the License, or
|
|
|
|
// (at your option) any later version.
|
|
|
|
//
|
|
|
|
// This program is distributed in the hope that it will be useful
|
|
|
|
// but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
// GNU Affero General Public License for more details.
|
|
|
|
//
|
|
|
|
// You should have received a copy of the GNU Affero General Public License
|
|
|
|
// along with this program. If not, see <http://www.gnu.org/licenses/>.
|
2015-06-30 23:15:48 -04:00
|
|
|
|
2016-08-18 19:23:42 -04:00
|
|
|
package cmd
|
2015-06-30 23:15:48 -04:00
|
|
|
|
|
|
|
import (
|
|
|
|
"net/http"
|
|
|
|
|
perf: websocket grid connectivity for all internode communication (#18461)
This PR adds a WebSocket grid feature that allows servers to communicate via
a single two-way connection.
There are two request types:
* Single requests, which are `[]byte => ([]byte, error)`. This is for efficient small
roundtrips with small payloads.
* Streaming requests which are `[]byte, chan []byte => chan []byte (and error)`,
which allows for different combinations of full two-way streams with an initial payload.
Only a single stream is created between two machines - and there is, as such, no
server/client relation since both sides can initiate and handle requests. Which server
initiates the request is decided deterministically on the server names.
Requests are made through a mux client and server, which handles message
passing, congestion, cancelation, timeouts, etc.
If a connection is lost, all requests are canceled, and the calling server will try
to reconnect. Registered handlers can operate directly on byte
slices or use a higher-level generics abstraction.
There is no versioning of handlers/clients, and incompatible changes should
be handled by adding new handlers.
The request path can be changed to a new one for any protocol changes.
First, all servers create a "Manager." The manager must know its address
as well as all remote addresses. This will manage all connections.
To get a connection to any remote, ask the manager to provide it given
the remote address using.
```
func (m *Manager) Connection(host string) *Connection
```
All serverside handlers must also be registered on the manager. This will
make sure that all incoming requests are served. The number of in-flight
requests and responses must also be given for streaming requests.
The "Connection" returned manages the mux-clients. Requests issued
to the connection will be sent to the remote.
* `func (c *Connection) Request(ctx context.Context, h HandlerID, req []byte) ([]byte, error)`
performs a single request and returns the result. Any deadline provided on the request is
forwarded to the server, and canceling the context will make the function return at once.
* `func (c *Connection) NewStream(ctx context.Context, h HandlerID, payload []byte) (st *Stream, err error)`
will initiate a remote call and send the initial payload.
```Go
// A Stream is a two-way stream.
// All responses *must* be read by the caller.
// If the call is canceled through the context,
//The appropriate error will be returned.
type Stream struct {
// Responses from the remote server.
// Channel will be closed after an error or when the remote closes.
// All responses *must* be read by the caller until either an error is returned or the channel is closed.
// Canceling the context will cause the context cancellation error to be returned.
Responses <-chan Response
// Requests sent to the server.
// If the handler is defined with 0 incoming capacity this will be nil.
// Channel *must* be closed to signal the end of the stream.
// If the request context is canceled, the stream will no longer process requests.
Requests chan<- []byte
}
type Response struct {
Msg []byte
Err error
}
```
There are generic versions of the server/client handlers that allow the use of type
safe implementations for data types that support msgpack marshal/unmarshal.
2023-11-20 20:09:35 -05:00
|
|
|
"github.com/minio/minio/internal/grid"
|
2023-01-23 06:12:47 -05:00
|
|
|
"github.com/minio/mux"
|
2015-06-30 23:15:48 -04:00
|
|
|
)
|
|
|
|
|
2020-06-12 23:04:01 -04:00
|
|
|
// Composed function registering routers for only distributed Erasure setup.
|
2020-12-01 16:50:33 -05:00
|
|
|
func registerDistErasureRouters(router *mux.Router, endpointServerPools EndpointServerPools) {
|
2019-11-22 15:45:13 -05:00
|
|
|
// Register storage REST router only if its a distributed setup.
|
perf: websocket grid connectivity for all internode communication (#18461)
This PR adds a WebSocket grid feature that allows servers to communicate via
a single two-way connection.
There are two request types:
* Single requests, which are `[]byte => ([]byte, error)`. This is for efficient small
roundtrips with small payloads.
* Streaming requests which are `[]byte, chan []byte => chan []byte (and error)`,
which allows for different combinations of full two-way streams with an initial payload.
Only a single stream is created between two machines - and there is, as such, no
server/client relation since both sides can initiate and handle requests. Which server
initiates the request is decided deterministically on the server names.
Requests are made through a mux client and server, which handles message
passing, congestion, cancelation, timeouts, etc.
If a connection is lost, all requests are canceled, and the calling server will try
to reconnect. Registered handlers can operate directly on byte
slices or use a higher-level generics abstraction.
There is no versioning of handlers/clients, and incompatible changes should
be handled by adding new handlers.
The request path can be changed to a new one for any protocol changes.
First, all servers create a "Manager." The manager must know its address
as well as all remote addresses. This will manage all connections.
To get a connection to any remote, ask the manager to provide it given
the remote address using.
```
func (m *Manager) Connection(host string) *Connection
```
All serverside handlers must also be registered on the manager. This will
make sure that all incoming requests are served. The number of in-flight
requests and responses must also be given for streaming requests.
The "Connection" returned manages the mux-clients. Requests issued
to the connection will be sent to the remote.
* `func (c *Connection) Request(ctx context.Context, h HandlerID, req []byte) ([]byte, error)`
performs a single request and returns the result. Any deadline provided on the request is
forwarded to the server, and canceling the context will make the function return at once.
* `func (c *Connection) NewStream(ctx context.Context, h HandlerID, payload []byte) (st *Stream, err error)`
will initiate a remote call and send the initial payload.
```Go
// A Stream is a two-way stream.
// All responses *must* be read by the caller.
// If the call is canceled through the context,
//The appropriate error will be returned.
type Stream struct {
// Responses from the remote server.
// Channel will be closed after an error or when the remote closes.
// All responses *must* be read by the caller until either an error is returned or the channel is closed.
// Canceling the context will cause the context cancellation error to be returned.
Responses <-chan Response
// Requests sent to the server.
// If the handler is defined with 0 incoming capacity this will be nil.
// Channel *must* be closed to signal the end of the stream.
// If the request context is canceled, the stream will no longer process requests.
Requests chan<- []byte
}
type Response struct {
Msg []byte
Err error
}
```
There are generic versions of the server/client handlers that allow the use of type
safe implementations for data types that support msgpack marshal/unmarshal.
2023-11-20 20:09:35 -05:00
|
|
|
registerStorageRESTHandlers(router, endpointServerPools, globalGrid.Load())
|
2016-12-10 03:42:22 -05:00
|
|
|
|
2019-03-14 19:27:31 -04:00
|
|
|
// Register peer REST router only if its a distributed setup.
|
2024-01-30 15:49:02 -05:00
|
|
|
registerPeerRESTHandlers(router, globalGrid.Load())
|
2019-03-14 19:27:31 -04:00
|
|
|
|
2023-01-03 11:16:39 -05:00
|
|
|
// Register peer S3 router only if its a distributed setup.
|
|
|
|
registerPeerS3Handlers(router)
|
|
|
|
|
2019-11-22 15:45:13 -05:00
|
|
|
// Register bootstrap REST router for distributed setups.
|
2024-01-24 16:36:44 -05:00
|
|
|
registerBootstrapRESTHandlers(globalGrid.Load())
|
2016-12-10 03:42:22 -05:00
|
|
|
|
2019-11-22 15:45:13 -05:00
|
|
|
// Register distributed namespace lock routers.
|
perf: websocket grid connectivity for all internode communication (#18461)
This PR adds a WebSocket grid feature that allows servers to communicate via
a single two-way connection.
There are two request types:
* Single requests, which are `[]byte => ([]byte, error)`. This is for efficient small
roundtrips with small payloads.
* Streaming requests which are `[]byte, chan []byte => chan []byte (and error)`,
which allows for different combinations of full two-way streams with an initial payload.
Only a single stream is created between two machines - and there is, as such, no
server/client relation since both sides can initiate and handle requests. Which server
initiates the request is decided deterministically on the server names.
Requests are made through a mux client and server, which handles message
passing, congestion, cancelation, timeouts, etc.
If a connection is lost, all requests are canceled, and the calling server will try
to reconnect. Registered handlers can operate directly on byte
slices or use a higher-level generics abstraction.
There is no versioning of handlers/clients, and incompatible changes should
be handled by adding new handlers.
The request path can be changed to a new one for any protocol changes.
First, all servers create a "Manager." The manager must know its address
as well as all remote addresses. This will manage all connections.
To get a connection to any remote, ask the manager to provide it given
the remote address using.
```
func (m *Manager) Connection(host string) *Connection
```
All serverside handlers must also be registered on the manager. This will
make sure that all incoming requests are served. The number of in-flight
requests and responses must also be given for streaming requests.
The "Connection" returned manages the mux-clients. Requests issued
to the connection will be sent to the remote.
* `func (c *Connection) Request(ctx context.Context, h HandlerID, req []byte) ([]byte, error)`
performs a single request and returns the result. Any deadline provided on the request is
forwarded to the server, and canceling the context will make the function return at once.
* `func (c *Connection) NewStream(ctx context.Context, h HandlerID, payload []byte) (st *Stream, err error)`
will initiate a remote call and send the initial payload.
```Go
// A Stream is a two-way stream.
// All responses *must* be read by the caller.
// If the call is canceled through the context,
//The appropriate error will be returned.
type Stream struct {
// Responses from the remote server.
// Channel will be closed after an error or when the remote closes.
// All responses *must* be read by the caller until either an error is returned or the channel is closed.
// Canceling the context will cause the context cancellation error to be returned.
Responses <-chan Response
// Requests sent to the server.
// If the handler is defined with 0 incoming capacity this will be nil.
// Channel *must* be closed to signal the end of the stream.
// If the request context is canceled, the stream will no longer process requests.
Requests chan<- []byte
}
type Response struct {
Msg []byte
Err error
}
```
There are generic versions of the server/client handlers that allow the use of type
safe implementations for data types that support msgpack marshal/unmarshal.
2023-11-20 20:09:35 -05:00
|
|
|
registerLockRESTHandlers()
|
|
|
|
|
|
|
|
// Add grid to router
|
|
|
|
router.Handle(grid.RoutePath, adminMiddleware(globalGrid.Load().Handler(), noGZFlag, noObjLayerFlag))
|
2016-12-10 03:42:22 -05:00
|
|
|
}
|
|
|
|
|
2023-07-08 10:31:42 -04:00
|
|
|
// List of some generic middlewares which are applied for all incoming requests.
|
|
|
|
var globalMiddlewares = []mux.MiddlewareFunc{
|
|
|
|
// set x-amz-request-id header and others
|
|
|
|
addCustomHeadersMiddleware,
|
|
|
|
// The generic tracer needs to be the first middleware to catch all requests
|
|
|
|
// returned early by any other middleware (but after the middleware that
|
|
|
|
// sets the amz request id).
|
|
|
|
httpTracerMiddleware,
|
|
|
|
// Auth middleware verifies incoming authorization headers and routes them
|
|
|
|
// accordingly. Client receives a HTTP error for invalid/unsupported
|
|
|
|
// signatures.
|
2021-11-01 11:04:03 -04:00
|
|
|
//
|
2021-01-04 12:54:22 -05:00
|
|
|
// Validates all incoming requests to have a valid date header.
|
2023-07-08 10:31:42 -04:00
|
|
|
setAuthMiddleware,
|
|
|
|
// Redirect some pre-defined browser request paths to a static location
|
|
|
|
// prefix.
|
|
|
|
setBrowserRedirectMiddleware,
|
|
|
|
// Adds 'crossdomain.xml' policy middleware to serve legacy flash clients.
|
|
|
|
setCrossDomainPolicyMiddleware,
|
2021-11-01 11:04:03 -04:00
|
|
|
// Limits all body and header sizes to a maximum fixed limit
|
2023-07-08 10:31:42 -04:00
|
|
|
setRequestLimitMiddleware,
|
2021-01-04 12:54:22 -05:00
|
|
|
// Validate all the incoming requests.
|
2023-07-08 10:31:42 -04:00
|
|
|
setRequestValidityMiddleware,
|
|
|
|
// Add upload forwarding middleware for site replication
|
|
|
|
setUploadForwardingMiddleware,
|
|
|
|
// Add bucket forwarding middleware
|
|
|
|
setBucketForwardingMiddleware,
|
|
|
|
// Add new middlewares here.
|
2018-04-04 22:07:54 -04:00
|
|
|
}
|
|
|
|
|
routers: Fix a crash while initializing network fs. (#1382)
Crash happens when 'minio server filename' a file name is
provided instead of a directory on command line argument.
```
panic: runtime error: slice bounds out of range
goroutine 1 [running]:
panic(0x5eb460, 0xc82000e0b0)
/usr/local/opt/go/libexec/src/runtime/panic.go:464 +0x3e6
main.splitNetPath(0x7fff5fbff9bd, 0x7, 0x0, 0x0, 0x0, 0x0)
/Users/harsha/mygo/src/github.com/minio/minio/network-fs.go:49 +0xb7
main.newNetworkFS(0x7fff5fbff9bd, 0x7, 0x0, 0x0, 0x0, 0x0)
/Users/harsha/mygo/src/github.com/minio/minio/network-fs.go:90 +0x20a
main.configureServerHandler(0xc82024e1c8, 0x5, 0xc8200640e0, 0x1, 0x1, 0x0, 0x0)
/Users/harsha/mygo/src/github.com/minio/minio/routers.go:43 +0x6ce
main.configureServer(0xc82024e1c8, 0x5, 0xc8200640e0, 0x1, 0x1, 0x5)
/Users/harsha/mygo/src/github.com/minio/minio/server-main.go:86 +0x67
```
2016-04-25 21:10:40 -04:00
|
|
|
// configureServer handler returns final handler for the http server.
|
2020-12-01 16:50:33 -05:00
|
|
|
func configureServerHandler(endpointServerPools EndpointServerPools) (http.Handler, error) {
|
2023-01-23 06:12:47 -05:00
|
|
|
// Initialize router. `SkipClean(true)` stops minio/mux from
|
2016-11-16 19:23:22 -05:00
|
|
|
// normalizing URL path minio/minio#3256
|
2020-02-11 22:38:02 -05:00
|
|
|
router := mux.NewRouter().SkipClean(true).UseEncodedPath()
|
2016-03-27 15:37:21 -04:00
|
|
|
|
2016-08-18 17:50:50 -04:00
|
|
|
// Initialize distributed NS lock.
|
2020-06-12 23:04:01 -04:00
|
|
|
if globalIsDistErasure {
|
2020-12-01 16:50:33 -05:00
|
|
|
registerDistErasureRouters(router, endpointServerPools)
|
2016-12-10 03:42:22 -05:00
|
|
|
}
|
2016-10-06 05:30:54 -04:00
|
|
|
|
2018-12-18 16:03:26 -05:00
|
|
|
// Add Admin router, all APIs are enabled in server mode.
|
2021-07-10 11:32:52 -04:00
|
|
|
registerAdminRouter(router, true)
|
2018-01-22 17:54:55 -05:00
|
|
|
|
2023-08-01 13:54:26 -04:00
|
|
|
// Add healthCheck router
|
2018-04-21 22:23:54 -04:00
|
|
|
registerHealthCheckRouter(router)
|
2018-03-12 02:16:53 -04:00
|
|
|
|
2018-04-18 19:01:42 -04:00
|
|
|
// Add server metrics router
|
2018-04-21 22:23:54 -04:00
|
|
|
registerMetricsRouter(router)
|
2018-04-18 19:01:42 -04:00
|
|
|
|
2020-12-28 20:10:33 -05:00
|
|
|
// Add STS router always.
|
|
|
|
registerSTSRouter(router)
|
2016-07-28 07:00:33 -04:00
|
|
|
|
2022-10-04 13:05:09 -04:00
|
|
|
// Add KMS router
|
|
|
|
registerKMSRouter(router)
|
|
|
|
|
2020-09-15 16:57:15 -04:00
|
|
|
// Add API router
|
|
|
|
registerAPIRouter(router)
|
2016-03-27 15:37:21 -04:00
|
|
|
|
2023-07-08 10:31:42 -04:00
|
|
|
router.Use(globalMiddlewares...)
|
2020-07-06 23:55:19 -04:00
|
|
|
|
2020-06-11 11:19:55 -04:00
|
|
|
return router, nil
|
2015-06-30 23:15:48 -04:00
|
|
|
}
|