Respect / Respect/Rest

Implement conditional requests: If-Match, If-Modified-Since, If-None-Match, If-Range, If-Unmodified-Since and Last-Modified

Open
#61 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
PHP
Stars
605
Forks
100
PR merge metrics
No merged PRs in 30d

Description

This feature is dependent on the implementation of the ETag see #40

Implement capabilities required for conditional requests:

Because these requests require knowledge of the actual response and to prevent us having to re-compose the response for every question this will benefit considerably from a server side cache solution as suggested in #60

Did I miss anything?

What are your thoughts, suggestions, special requirements? Do you know of any current implementations we might benefit from referencing? Warnings? Concerns? Are you able to help?

Get involved and you can also be part of making Respect/Rest even more awesome than it is, there is more than enough ways for you to help, feel free to contact any of the Respect developers if you need help getting involved!

Also a big thank you to our current supporters you guys rock! Keep up the good work!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the dependent ETag implementation in issue #40 and the server-side cache proposal in issue #60, then consult the linked RFC sections for each conditional-request header. Done means the REST implementation supports If-Match, If-Modified-Since, If-None-Match, If-Range, If-Unmodified-Since, and Last-Modified using the relevant response information.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.