Libraries tagged by not-found

Allow not found records in PersistedAliasMapper

Go to Download

A concrete5 8.4.0+ add-on to quickly return a 404-response if a file isn't found.

Go to Download

Smart Router for invalid URIs

Go to Download

Dropbox File Upload

Go to Download

Email alerts to system admin on 404 URL visits

Go to Download

Unserializes php serialized strings and is able the process class that are not loaded

Go to Download

Simple script for checking http code of URL list and filter if necessary. Can be easy used for checking 404 codes for site and getting list of 404 error pages.

Go to Download

Grinet NotFoundCode is a Magento 2 module that allows you to change the default 404 HTTP status code to a different one (such as 410) for SEO purposes.

Go to Download

Check the response code of the page. Checking for 404 errors on the site.

Go to Download

Page Not Found handling without configuration. Handle redirect to other domains when pages were moved.

Go to Download

Enables simple 404 Page NotFound handling, also for multilingual sites.

Go to Download

Check the health of a URL. Does it return 200 OK? 404 Not Found? Does in redirect indefinitely?

Go to Download

A drop-in replacement for the Laravel translator which emits warnings and errors when translations had to fall back or were not found

Go to Download

Throws exception on translation not found and invalid doctrine schema.

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download