Libraries tagged by urlencode

Middleware to parse the body of the request with support for json, csv and url-encode

Go to Download

A library to validate strings and transliterate to ascii encoding

Go to Download

Allow Urlencoded slashed and more in routing parameters

Go to Download

Allow Urlencoded slashed and more in routing parameters

Go to Download

PHP兼容Java的urlencode实现

Go to Download

A minimal PHP library to nativly support PUT, PATCH and DELETE user input in form of mutlipart/form-data, application/x-www-form-urlencoded and various JSON types like application/json with complex data structures (nested html forms).

Go to Download

[1] Add support for `application/wubinworks-x-www-form-urlencoded`. [2] Conditionally modifies JSON output behavior. See https://github.com/wubinworks/magento2-module-webapi

Go to Download

Provides base64_url_encode/base64_url_decode.

Go to Download

Mock Java's urlEncode implementation by PHP

Go to Download

Allow Urlencoded slashed and more in routing parameters

Go to Download

Simple Guzzle 6.x URL-encoded response middleware

Go to Download

Tools for modifying strings.

Go to Download

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download

Provides a Doctrine Cache adapter for the Rollerworks URIEncoder Component

Go to Download

PHP psr7 stream decorators for mime message part streams

Go to Download