Libraries tagged by URL safe

YOURLS plugin which updates the long URL of an existing keyword, or creates a new short URL with the supplied keyword

Go to Download

Magento 2 fixes: CMS Page saving fails with 'The value specified in the URL Key field would generate a URL that already exists.'

Go to Download

Yii Extension to translate unsave string to save for url and filename

Go to Download

Make your link simple

Go to Download

Provides utilities required for signing and authenticating calls to public URLs.

Go to Download

Nette extension for simply redirecting user to the same url with different schema

Go to Download

Bundle that saves URL tracking value (if there's any) to specified storage (cookie, session, cache)

Go to Download

Save a URL to redirect the user later

Go to Download

A Laravel Nova tool used to save shorten url links in your bitly accout through nova-admin panel.

Go to Download

This module for Magento 2 helps to download an image from external URL for further save it as a product media gallery entry.

Go to Download

Contains some useful tools like a testing tool for redirects, a link checker, a back link checker and a content comparison tool between the same or different urls. Furthermore there is full scheduler support for all tests and synchronization tasks.

Go to Download

This bundle allow you to save utm parameters from url into a cookie when they exists. It's also provide a bunch of tools to easily retrive all or each utm.

Go to Download

Download, save & manage atom feeds from specified URL

Go to Download

Convert HAR files saved from Chrome developer tools to URL list

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