microsoft/restler-fuzzer

Handle 202 from DELETE requests in the garbage collector

Open

#655 opened on Oct 13, 2022

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Python (329 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (2,929 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

The garbage collector currently accepts 202 as a deletion success code - it needs to handle 202s in the same way as in the main algorithm and retrieve the status from the Location: header.

Contributor guide

Research direction
Examine the main algorithm's handling of 202 responses and replicate the logic in the garbage collector to retrieve status from the Location header.
Tech stack
python
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75