You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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: