follow up to microsoft/kiota#4367
and microsoft/kiota#4190

Implement a unit test with a 304 response, no location header, check the request adapter returns null and doesn't throw.

related to microsoft/kiota#4025
add a 3rd case in the error handling of the request adapter for XXX (must be the 3rd in the order, first sepcific code, then 4XX or 5XX depending on the first number, then XXX)

originally reported in microsoft/kiota-http-python#179
We add those cases as unit tests and correct the implementation so it doesn't impact query parameters values

Follow up of microsoft/kiota#1699 for PHP.
No generation changes required (hence the issue being created over here). Only the runtime rules need to be implemented/validated. (see the linked PRs for examples).

Hi,
I've came across a problem, where querying Graph API caused my program to „freeze“. I suspected retry handler to be a problem and dug into the code.
In the RetryHandler I see, that there is a Guzzle option delay set here and here. The variable $delaySecs bears delay value in seconds, but Guzzle delay options accepts delay parameter in milliseconds.

Shouldn't the delaySecs be passed in milliseconds rather than seconds?

The Microsoft\Kiota\Http\GuzzleRequestAdapter constructor requires an instance of the GuzzleHttp\Client class. By typehinting to a concrete implementation (especially one that is annotated as final), this makes using custom implementations next to impossible (especially should the Guzzle maintainers add the final keyword to the class declaration). Instead, the GuzzleHttp\ClientInterface should be typehinted against as the implementation does not rely on features specific to the concrete class.