Os status codes na faixa dos 400 significam que houve um erro por parte do cliente.

Você se lembra de todos aqueles erros (e piadas) a respeito do "**404 Not Found**"?

## Use o `HTTPException` { #use-httpexception }

Para retornar ao cliente *responses* HTTP com erros, use o `HTTPException`.

### Import `HTTPException` { #import-httpexception }

// error returned when temporary account is not found
var errNoSuchTempAccount = errors.New("Specified temporary account does not exist")

// error returned when access key is not found
var errNoSuchAccessKey = errors.New("Specified access key does not exist")

// error returned in IAM subsystem when an account doesn't exist.

func Errorf(format string, a ...any) error {
	e := fmt.Errorf(format, a...)
	ee := Error{}
	ee.msg = e.Error()
	ee.cause = errors.Unwrap(e)
	return ee
}

// Unwrap the internal error.
func (e Error) Unwrap() error { return e.cause }

// Error 'error' compatible method.
func (e Error) Error() string {
	if e.msg == "" {
		return "crypto: cause <nil>"
	}
	return e.msg
}

var (

        }
    ]
}
```

you will get a text version, with:

```
Validation errors:
Field: ('path', 'item_id'), Error: Input should be a valid integer, unable to parse string as an integer
```

### Override the `HTTPException` error handler { #override-the-httpexception-error-handler }

The same way, you can override the `HTTPException` handler.

		if netErr, ok := err.(*net.OpError); ok {
			return ErrPortAccess(netErr).Msg("Insufficient permissions to use specified port")
		}
	}

	// Failed to identify what type of error this, return a simple UI error
	return Err{msg: err.Error()}
}

// FmtError converts a fatal error message to a more clear error
// using some colors
func FmtError(introMsg string, err error, jsonFlag bool) string {

}

// toAPIErrorCode - Converts embedded errors. Convenience
// function written to handle all cases where we have known types of
// errors returned by underlying layers.
func toAPIErrorCode(ctx context.Context, err error) (apiErr APIErrorCode) {
	if err == nil {
		return ErrNone
	}

	// Errors that are generated by net.Conn and any context errors must be handled here.

        }
    ]
}
```

eine Textversion mit:

```
Validation errors:
Field: ('path', 'item_id'), Error: Input should be a valid integer, unable to parse string as an integer
```

### Überschreiben des `HTTPException`-Fehlerhandlers { #override-the-httpexception-error-handler }

Auf die gleiche Weise können Sie den `HTTPException`-Handler überschreiben.

        }
    ]
}
```

вы получите текстовую версию:

```
Validation errors:
Field: ('path', 'item_id'), Error: Input should be a valid integer, unable to parse string as an integer
```

### Переопределите обработчик ошибок `HTTPException` { #override-the-httpexception-error-handler }

Аналогичным образом можно переопределить обработчик `HTTPException`.

        }
    ]
}
```

obtendrás una versión en texto, con:

```
Validation errors:
Field: ('path', 'item_id'), Error: Input should be a valid integer, unable to parse string as an integer
```

### Sobrescribir el manejador de errores de `HTTPException` { #override-the-httpexception-error-handler }

De la misma manera, puedes sobrescribir el manejador de `HTTPException`.

        }
    ]
}
```

ви отримаєте текстову версію:

```
Validation errors:
Field: ('path', 'item_id'), Error: Input should be a valid integer, unable to parse string as an integer
```

### Перевизначення обробника помилок `HTTPException` { #override-the-httpexception-error-handler }

Аналогічно, ви можете перевизначити обробник `HTTPException`.