Ensure Chrome browser usage only for GET requests#197
Merged
Conversation
Added a screenshot browser action. Therefor extended the `RespondedRequest` class, so it also transports the paths of the screenshots on the filesystem. Also added two new methods to the `Http` steps allowing to modify the loader, only for one particular step in the chain. They can be used to skip the configured cache or to switch to use the (headless) Chrome browser.
Since the Chrome browser can only execute GET requests: - The loader now automatically switches to the HTTP client for POST, PUT, PATCH, and DELETE requests, logging a warning. - A warning is logged when attempting to use 'Post Browser Navigate Hooks' with these request types. - Consequently, the `useBrowser()` method, introduced in v3.4.0, is also limited to GET requests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since the Chrome browser can only execute GET requests:
useBrowser()method, introduced in v3.4.0, is also limited to GET requests.