MarketSquare / MarketSquare/roboswag
ProxyError: Cannot connect to proxy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 29
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Dear Mateusz,
thank you for your hard work and contributions to the RF community!
we were beyond excited to try the tool at work, however I am having issues to make the SwaggerPetshop example to work. I am not able to connect to proxy from the company's laptop (while having heavy security measurements in place).
Using OperatingSystem's Set Environment Variable to set both HTTP_PROXY and HTTPS_PROXY within the test case does not seem to work either.
The error:
ProxyError: HTTPSConnectionPool(host='petstore3.swagger.io', port=443): Max retries exceeded with url: /api/v3/pet/findByStatus?status=available (Caused by ProxyError('Cannot connect to proxy.', FileNotFoundError(2, 'No such file or directory')))
Thank you for looking into this,
Tereza
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the SwaggerPetshop example on a machine with the reported company proxy restrictions, using OperatingSystem to set HTTP_PROXY and HTTPS_PROXY. No source file or test is named, so trace how the example and its HTTP client consume those variables and compare the result with the reported ProxyError; done means the example connects through the proxy or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100