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

[🐛 Bug]: Selenium interception Response body is getting mocked but not response code #15422

Open
Mohanram3012 opened this issue Mar 14, 2025 · 2 comments

Comments

@Mohanram3012
Copy link

What happened?

driver.intercept do |request, &continue|
end
can perfectly replace the response body but not the response code.
With the code below, I can get the intercepted body, but the response code is still 404 (I hope it to be 200)

How can we reproduce the issue?

require 'selenium-webdriver'

driver = Selenium::WebDriver.for :remote, url: "http://localhost:4444/wd/hub", capabilities: :chrome
driver.intercept do |request, &continue|
    uri = URI(request.url)
    if uri.path.end_with?('/not_exist.html')
        continue.call(request) do |r|
            r.code = 200
            r.body = "intercepted"
        end
    else
        continue.call(request)
    end
end

sleep 20
driver.navigate.to "http://www.google.com/not_exist.html"
sleep 20

driver.quit

Relevant log output

NA

Operating System

Mac

Selenium version

4.10

What are the browser(s) and version(s) where you see this issue?

chrome133

What are the browser driver(s) and version(s) where you see this issue?

chromedriver133

Are you using Selenium Grid?

NO

Copy link

@Mohanram3012, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

@Mohanram3012
Copy link
Author

The issue is already reported but couldn't get proper resolution out of it -> #11332

@pujagani pujagani added the C-rb label Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants