Skip to content

🚀 Add allow_forbidden_requests option in HarnessOptions#114

Open
mohamedmamdouh22 wants to merge 1 commit intomainfrom
allow-forbidden-requests
Open

🚀 Add allow_forbidden_requests option in HarnessOptions#114
mohamedmamdouh22 wants to merge 1 commit intomainfrom
allow-forbidden-requests

Conversation

@mohamedmamdouh22
Copy link
Copy Markdown
Contributor

@mohamedmamdouh22 mohamedmamdouh22 commented Feb 13, 2025

  • Changed the timeout parameter in the capture_url function from Optional[int] to int.
  • Added a check for allow_forbidden_requests in the run function to handle requests with status codes >= 400 only if the option is not set.
  • Added a new allow_forbidden_requests field to the HarnessOptions class.

Important

Add allow_forbidden_requests option to HarnessOptions and modify run() behavior in core.py to handle HTTP status codes based on this option.

  • Behavior:
    • Added allow_forbidden_requests option to HarnessOptions in types.py.
    • Modified run() in core.py to skip error handling for status codes >= 400 if allow_forbidden_requests is set.
    • Changed timeout parameter in capture_url() in core.py from Optional[int] to int.
  • Versioning:
    • Updated version to 0.60.2 in pyproject.toml and uv.lock for both harambe-core and harambe-sdk.

This description was created by Ellipsis for f87c504. It will automatically update as commits are pushed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant