Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Misleading documentation in requests URI

See original GitHub issue

I tried to use Get Request keyword in 0.8, but something is broken, I’m no able to put URI, it’s support only path.

In documentation it’s information about “URI” not path so I tryied: Get Request sess https://mydomain.com/test, but result is https://mydomain.com/https://mydomain.com/test. Same problem with Get On Session

Issue Analytics

State:
Created 3 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

lucagiovecommented, Apr 20, 2021

Ok now the behavior is more rfc compliant but slightly different from the past. To have the right behavior you’ve to write the test in this way:

Create Session    sess    https://mydomain.com/dev/
GET On Session    sess    test

0reactions

cloutierjocommented, Apr 20, 2021

This actually cause a new issue. We did use the lib in this way:

Create Session sess https://mydomain.com/dev
GET On Session sess /test

Which does a GET on https://mydomain.com/dev/test , Now it’s doing it on https://mydomain.com/test which obviously fail. I’m not sure if the way we were using it should be supported going forward, but at least it should be marked as breaking change in the 0.9 version. Thought I would prefer to keep the old behaviour as it makes it easy to switch our test between different environment that does not always have the same base path (/dev might be /test or /…).

Top Results From Across the Web

V2: incorrect documentation for original uri placeholders ...

Hi, Just to let you know that this documentation page indicates that the request's original URI placeholder is {http.request.orig.uri}, ...

Understanding URI Hosting Practice as Support for URI ... - W3C

The purpose of defining which representations are to be considered nominal URI documentation carriers is to coordinate uses of the URI.

Student Handbook - The University of Rhode Island

Providing incorrect, untruthful or incomplete information in response to legitimate requests by University officials or conduct boards is prohibited.

urllib.request — Extensible library for opening URLs — Python ...

Open the URL url, which can be either a string or a Request object. ... of the response headers as it is specified...

RFC 3986: Uniform Resource Identifier (URI): Generic Syntax

1. User Information The userinfo subcomponent may consist of a user name and, optionally, scheme-specific information about how to gain authorization to access ......