Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Curl - allow setting HTTP version #19845

Merged
merged 1 commit into from Feb 10, 2019
Merged

Curl - allow setting HTTP version #19845

merged 1 commit into from Feb 10, 2019

Conversation

ghost
Copy link

@ghost ghost commented Dec 17, 2018

Description

Added allow for setting curl http version

Fixed Issues (if relevant)

  1. Magento/Framework/HTTP/Adapter/Curl.php doesn't allow setting HTTP version #19442: Magento/Framework/HTTP/Adapter/Curl.php doesn't allow setting HTTP version

Manual testing scenarios (*)

  1. Create new ZendClient $client
  2. Set HTTP version $client->setConfig(['httpversion' => CURL_HTTP_VERSION_1_1])
  3. Make a request $client->request()

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

Additional information

  1. Curl - allow setting HTTP version #19445: Recovered Pull Request

@magento-engcom-team
Copy link
Contributor

Hi @SikailoISM. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@magento-engcom-team magento-engcom-team added Component: Framework/HTTP Release Line: 2.3 Partner: ISM eCompany Pull Request is created by partner ISM eCompany partners-contribution Pull Request is created by Magento Partner labels Dec 17, 2018
@ghost ghost mentioned this pull request Dec 17, 2018
4 tasks
@magento-engcom-team
Copy link
Contributor

Hi @sivaschenko, thank you for the review.
ENGCOM-3710 has been created to process this Pull Request

@ryanreeves-taxjar
Copy link

Is it possible to bypass the Codacy/PR Quality Review? It fails on the use of curl_setopt, but I don't think that guideline should apply since the write method already calls that function several times.

@sivaschenko
Copy link
Member

Hi @ryanreeves-taxjar , yes, I think that codacy can be ignored in this particular case.

@perfpcs
Copy link

perfpcs commented Jan 14, 2019

Can I get an update when this issue will be resolved? It seems like this will happen in 2,3.1, correct? What is the estimate time release for 2.3.1?

@okorshenko okorshenko removed this from the Release: 2.3.1 milestone Jan 28, 2019
@sivaschenko
Copy link
Member

Hi @SikailoISM , sorry for delays in processing and response, it will be soon merged to mainline

@ghost
Copy link

ghost commented Feb 10, 2019

Hi @SikailoISM, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@joni-jones
Copy link
Contributor

This fix breaks existing functionality, curl_setopt with CURLOPT_HTTP_VERSION requires a digit 0-3 but not a string. See http://php.net/manual/en/function.curl-setopt.php

@ghost ghost mentioned this pull request Feb 15, 2019
4 tasks
@ghost ghost deleted the 2-3-Curl-allow-setting-HTTP-version branch February 15, 2019 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Award: bug fix Component: Framework/HTTP Partner: ISM eCompany Pull Request is created by partner ISM eCompany partners-contribution Pull Request is created by Magento Partner Progress: accept Release Line: 2.3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants