-
Notifications
You must be signed in to change notification settings - Fork 668
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
Difference in response between v1 and v2 #3866
Labels
Comments
Likely a missing feature. Will see if we can add support for this soon. |
Hello, sorry for disturbing, but is there any updates on this? |
Hello, any updates on this? |
Sorry for the delay :/. This is actually intended behavior. The API is designed to not return a Request: {
"url": "https://example.com/",
"elements": [
{ "selector": "h1" }
],
"debugOpts": {
}
} response {
"data": [
{
"results": [
// ...
],
"selector": "h1"
}
],
"debug": {
"console": [],
"network": {
"inbound": [],
"outbound": []
}
}
} |
@Umzario feel free to reopen this one if you have any other issues |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hey guys, I notice a minor bug while testing out v2. When using the /scrape endpoint in v1 to retrieve content for a URL (we'll take www.example.com as an example URL), I can see the response headers for each inbound/outbound network (response["debug"]["network"]["inbound"]), however, in v2, the response headers don't appear to be visible. Is this a bug or am i missing something? Please let me know if more is needed. Thanks in advance
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Response headers for inbound/outbound network requests can be found
Screenshots
Here's inbound network in v1:
[{'status': 200, 'url': 'https://www.example.com/', 'headers': {'accept-ranges': 'bytes', 'age': '480002', 'cache-control': 'max-age=604800', 'content-encoding': 'gzip', 'content-length': '648', 'content-type': 'text/html; charset=UTF-8', 'date': 'Wed, 21 Feb 2024 14:27:46 GMT', 'etag': '"3147526947"', 'expires': 'Wed, 28 Feb 2024 14:27:46 GMT', 'last-modified': 'Thu, 17 Oct 2019 07:18:26 GMT', 'server': 'ECS (dce/26AB)', 'vary': 'Accept-Encoding', 'x-cache': 'HIT'}}]
Here's inbound network in v2:
[{'status': 200, 'url': 'https://www.example.com/'}]
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: