summaryrefslogtreecommitdiff
path: root/lib/chef/http.rb
Commit message (Collapse)AuthorAgeFilesLines
* chefstyle: fix Lint/StringConversionInInterpolationLamont Granquist2016-01-121-1/+1
| | | | useless use of `"#{foo.to_s}"`
* expose HTTP optionstm/fix_reg_tests_2Thom May2015-12-091-0/+2
| | | | and use it in registration client specs
* Merge pull request #4130 from chef/lcg/lazy-socketless-requireLamont Granquist2015-11-041-2/+9
|\ | | | | lazy the socketless require in Chef::HTTP
| * thread-safe performant lazy requirelcg/lazy-socketless-requireLamont Granquist2015-11-041-1/+5
| |
| * add more verbose info/clarity to comment blockLamont Granquist2015-11-041-2/+3
| |
| * lazy the socketless require in Chef::HTTPLamont Granquist2015-11-041-2/+4
| | | | | | | | | | | | | | | | | | if this is always required then everything that uses Chef::HTTP will load up chef-zero which will load up Webrick, which does DNS lookups of the current host which causes a DNS lookup and possible timeout. it also likely isn't doing pretty things to chef-client memory usage and load times there as well.
* | Add connection resets to HTTP retry casesdanielsdeleo2015-11-041-1/+1
| |
* | Skip retries of certificate verification failuresdanielsdeleo2015-11-041-1/+1
| |
* | Re-raise SSL errors after retry w/ correct classdanielsdeleo2015-11-041-2/+2
| |
* | Add in retry for possible transient SSL errorsglasschef2015-11-041-0/+7
|/
* Add --no-listen option to disable zero binding to portdanielsdeleo2015-04-011-0/+1
|
* Extract Chef Zero code out to chef zero, re-enable socket listeningdanielsdeleo2015-04-011-1/+1
|
* Hoist socketless chef-zero support into Chef::HTTPdanielsdeleo2015-04-011-2/+11
| | | | | | Was hoping to avoid this, but there are multiple subclasses of Chef::HTTP that interact with the server, which all must support socketless mode.
* Fix. Make sure that scheme part of the URI is treated in a case-insensitive ↵Krzysztof Wilczynski2014-12-291-1/+1
| | | | | | | | | | manner. This is as per http://en.wikipedia.org/wiki/URI_scheme, and solves some edges i.e., following (30x) URL from the "Location" header where we have to deal with "HTTP://". Signed-off-by: Krzysztof Wilczynski <krzysztof.wilczynski@linux.com>
* Remove 1.8 and 1.9 specific monkey patchesdanielsdeleo2014-11-261-1/+0
|
* Merge pull request #1827 from svanharmelen/fix-redirect-bugSerdar Sutay2014-10-101-1/+1
|\ | | | | Fix a bug when receiving a relative redirect location
| * Updated the code after discussing with @btm, @lamont-granquist and ↵Sander van Harmelen2014-09-091-4/+1
| | | | | | | | @danielsdeleo
| * Fix a bug when receiving a relative redirect locationSander van Harmelen2014-08-191-0/+3
| | | | | | | | | | | | Currently when you use a provider that somewhere along the line uses Chef::HTTP.request or Chef::HTTP.streaming_request, you will receive an error when the response is a redirect with a relative location.
* | read http_retry_count from chef config in the spec; add HTTP error code in ↵Hui Hu2014-09-041-1/+1
| | | | | | | | the log.
* | retry on HTTP 50X Error when calling Chef REST APIHui Hu2014-08-251-12/+19
| |
* | Revert "add retries in additional cases"Lamont Granquist2014-08-231-19/+5
| | | | | | | | | | | | Pushed straight to master again, I need to stop coding... This reverts commit fb58236637095e22f25ed17143e435f4a58d7d6c.
* | add retries in additional casesLamont Granquist2014-08-231-5/+19
|/
* Add missing requires to HTTP and HTTP::Simplehttp-simple-requiresdanielsdeleo2014-06-271-0/+2
|
* Merge pull request #1396 from svanharmelen/CHEF-5261Claire McQuin2014-06-091-1/+4
|\ | | | | CHEF-5261 Added some tests to prevent double slashes
| * COOK-5261 Added some formatting to prevent malformed URLsSander van Harmelen2014-05-131-1/+4
| |
* | CHEF-5198: a better fixLamont Granquist2014-04-091-9/+7
|/ | | | | | | | - reverts previous fix to CHEF-5198 - applies stream handler middleware in (proper) reverse order - adds debugging around middleware application - moves dumping of response header debugging to before applying response/streaming middleware
* CHEF-5100:Lamont Granquist2014-03-271-4/+0
| | | | | | - Enable Content Validation Check for Chef::HTTP::Simple - Tidy up debug logs / comments - More specs.
* CHEF-5041: check for transfer-encoding headerLamont Granquist2014-03-271-0/+3
| | | | | | - skip content-length check in the presence of a transfer-encoding header - also adds debugging and some refactoring
* validate streaming file sizeClaire McQuin2014-01-231-8/+18
|
* Support HTTP req to base URL without adding a slashdanielsdeleo2013-10-161-0/+2
| | | | | | | For single use HTTP clients, you can now do, e.g., http = Chef::HTTP::Simple.new("http://opscode.com/document.txt") http.get And no trailing slash is added.
* Return the response body by default if we've read itdanielsdeleo2013-10-161-1/+3
| | | | | Otherwise clients like HTTP::Simple don't return anything at all from http requests
* Use new Chef::ServerAPI API class in upload/download/diffJohn Keiser2013-10-091-8/+11
|
* Fix Chef::HTTP dependence on subclass methodsdanielsdeleo2013-10-081-11/+11
|
* Move streaming requests to generic HTTP classdanielsdeleo2013-10-081-12/+99
|
* Refactor HTTP streaming to reuse base implementationsdanielsdeleo2013-10-081-5/+10
|
* HTTP client creates request objects.danielsdeleo2013-10-081-17/+21
| | | | | | | Changes the structure of HTTP requests so that we create an HTTP client object and then ask it to make requests. This allows for easier customization of the HTTP client object, in particular enabling use to make use of persistent connections.
* Remove references to authenticator from base HTTP classdanielsdeleo2013-10-081-6/+2
|
* Top-level HTTP object doens't deal with cookies nowdanielsdeleo2013-10-081-2/+1
|
* Move HTTP components into chef/httpdanielsdeleo2013-10-081-0/+288
View Lorry Controller Status