From 5bfdf3f05fd2da7c305b31012e0bdf9d636fa20d Mon Sep 17 00:00:00 2001
From: Daniel Gerhardt <code@dgerhardt.net>
Date: Sat, 1 Aug 2015 12:19:56 +0200
Subject: [PATCH] Use PUT instead of PATCH method for updates to features
All feature settings are replaced by the received object so the use of
PATCH does not make sense here. The session is "patched" but the HTTP
verb always relates to the URL which refers explicitly to features in
this case.
See https://tools.ietf.org/html/rfc5789.
---
src/main/java/de/thm/arsnova/controller/SessionController.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/main/java/de/thm/arsnova/controller/SessionController.java b/src/main/java/de/thm/arsnova/controller/SessionController.java
index 3ef4c036..5dd16d2a 100644
--- a/src/main/java/de/thm/arsnova/controller/SessionController.java
+++ b/src/main/java/de/thm/arsnova/controller/SessionController.java
@@ -265,7 +265,7 @@ public class SessionController extends PaginationController {
return sessionService.getSessionFeatures(sessionkey);
}
- @RequestMapping(value = "/{sessionkey}/features", method = RequestMethod.PATCH)
+ @RequestMapping(value = "/{sessionkey}/features", method = RequestMethod.PUT)
public SessionFeature changeSessionFeatures(
@PathVariable final String sessionkey,
@RequestBody final SessionFeature features,
--
GitLab