blob: edbb5ab7f27a050fda42263ede57f3475a0c5792 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [99s-extend] Prevent resource creation on POST
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Prevent%20resource%20creation%20on%20POST&In-Reply-To=%3C5430F7EC.4080306%40ninenines.eu%3E">
<META NAME="robots" CONTENT="index,nofollow">
<style type="text/css">
pre {
white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
}
</style>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000468.html">
<LINK REL="Next" HREF="000470.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[99s-extend] Prevent resource creation on POST</H1>
<B>Loïc Hoguin</B>
<A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Prevent%20resource%20creation%20on%20POST&In-Reply-To=%3C5430F7EC.4080306%40ninenines.eu%3E"
TITLE="[99s-extend] Prevent resource creation on POST">essen at ninenines.eu
</A><BR>
<I>Sun Oct 5 09:49:00 CEST 2014</I>
<P><UL>
<LI>Previous message: <A HREF="000468.html">[99s-extend] Prevent resource creation on POST
</A></li>
<LI>Next message: <A HREF="000470.html">[99s-extend] PUT on new resource and status 201
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#469">[ date ]</a>
<a href="thread.html#469">[ thread ]</a>
<a href="subject.html#469">[ subject ]</a>
<a href="author.html#469">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>If resource_exists = true, then POST doesn't create but update the
resource at the given URI. If what you are doing is something like
write-once resources then you will have to reject these cases manually
by returning halt at some point.
On 10/05/2014 05:56 AM, Amol Hatwar wrote:
><i> Hello,
</I>><i>
</I>><i> I was recently tinkering with cowboy_rest and found that there is no way prevent resource creation in a POST request when it already exists. Either that, or I'm probably not doing something right or don't know enough...
</I>><i>
</I>><i> Here's what I have running:
</I>><i> A user tries to signup with a post request. To be successful, the username has to be unique. The resource_exists/2 method responds with proper true and false values by looking at the request body.
</I>><i>
</I>><i> Here's what I want done:
</I>><i> Iff the resource_exists callback returns true, I don't want the AcceptResource callback to run at all. Instead, I want to send a 4XX status and halt. Is there a canonical way of doing this?
</I>><i>
</I>><i> Cheers,
</I>><i>
</I>><i> AH
</I>><i> _______________________________________________
</I>><i> Extend mailing list
</I>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A>
</I>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">https://lists.ninenines.eu/listinfo/extend</A>
</I>><i>
</I>
--
Loïc Hoguin
<A HREF="http://ninenines.eu">http://ninenines.eu</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000468.html">[99s-extend] Prevent resource creation on POST
</A></li>
<LI>Next message: <A HREF="000470.html">[99s-extend] PUT on new resource and status 201
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#469">[ date ]</a>
<a href="thread.html#469">[ thread ]</a>
<a href="subject.html#469">[ subject ]</a>
<a href="author.html#469">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>
|
