Title: Why limit the the response status codes that would trigger a notification? · Issue #1 · solid/solid-prep · GitHub
Open Graph Title: Why limit the the response status codes that would trigger a notification? · Issue #1 · solid/solid-prep
X Title: Why limit the the response status codes that would trigger a notification? · Issue #1 · solid/solid-prep
Description: The spec defines that PUT/PATCH/DELETE requests should only trigger a notification when the server responds with a 200/204. Why the specific limitation to those status codes instead of just saying a successful request? When a PUT/PATCH c...
Open Graph Description: The spec defines that PUT/PATCH/DELETE requests should only trigger a notification when the server responds with a 200/204. Why the specific limitation to those status codes instead of just saying ...
X Description: The spec defines that PUT/PATCH/DELETE requests should only trigger a notification when the server responds with a 200/204. Why the specific limitation to those status codes instead of just saying ...
Opengraph URL: https://github.com/solid/solid-prep/issues/1
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Why limit the the response status codes that would trigger a notification?","articleBody":"The spec defines that PUT/PATCH/DELETE requests should only trigger a notification when the server responds with a 200/204. Why the specific limitation to those status codes instead of just saying a successful request? When a PUT/PATCH creates a resource the status code would be 201 for example. And the CSS returns a 205 when those update an existing resource.\r\n\r\nRelated: https://github.com/solid/specification/issues/288","author":{"url":"https://github.com/joachimvh","@type":"Person","name":"joachimvh"},"datePublished":"2023-10-25T06:39:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/1/solid-prep/issues/1"}| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:e643d9f6-a183-6ec4-d96d-14ed20f74d91 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B488:109CA2:86A472:B0CA4E:698EC2EE |
| html-safe-nonce | ea96b1a86df471ac4cfca40618272e8a9911adea660f4c97fcac26518f90f61b |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCNDg4OjEwOUNBMjo4NkE0NzI6QjBDQTRFOjY5OEVDMkVFIiwidmlzaXRvcl9pZCI6IjY5NTE1MjU3MjcwNzk0MTY1NTgiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 9a3571be58cbd92aceb98aa07d89b07344f1f201fbb9b446582867285fd6fa5c |
| hovercard-subject-tag | issue:1960655076 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/solid/solid-prep/1/issue_layout |
| twitter:image | https://opengraph.githubassets.com/2d4cc41cdbebcc4f1e64a1a864dbf809910d78be13b43fce6ebe840fc47f1252/solid/solid-prep/issues/1 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/2d4cc41cdbebcc4f1e64a1a864dbf809910d78be13b43fce6ebe840fc47f1252/solid/solid-prep/issues/1 |
| og:image:alt | The spec defines that PUT/PATCH/DELETE requests should only trigger a notification when the server responds with a 200/204. Why the specific limitation to those status codes instead of just saying ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | joachimvh |
| hostname | github.com |
| expected-hostname | github.com |
| None | cb2828a801ee6b7be618f3ac76fbf55def35bbc30f053a9c41bf90210b8b72ba |
| turbo-cache-control | no-preview |
| go-import | github.com/solid/solid-prep git https://github.com/solid/solid-prep.git |
| octolytics-dimension-user_id | 14262490 |
| octolytics-dimension-user_login | solid |
| octolytics-dimension-repository_id | 707601272 |
| octolytics-dimension-repository_nwo | solid/solid-prep |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 707601272 |
| octolytics-dimension-repository_network_root_nwo | solid/solid-prep |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | e6b91a7e6e46287d26887e3fb7a4161657bab8f7 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width