summaryrefslogtreecommitdiffstats
path: root/archives/extend/2014-February/000327.html
blob: d9e2859b73895893563d6cd00eb29210c1feabe3 (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
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
 <HEAD>
   <TITLE> [99s-extend] Accept header in POST request
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Accept%20header%20in%20POST%20request&In-Reply-To=%3C52EFE203.4020702%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="000326.html">
   <LINK REL="Next"  HREF="000328.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[99s-extend] Accept header in POST request</H1>
    <B>Lo&#239;c Hoguin</B> 
    <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Accept%20header%20in%20POST%20request&In-Reply-To=%3C52EFE203.4020702%40ninenines.eu%3E"
       TITLE="[99s-extend] Accept header in POST request">essen at ninenines.eu
       </A><BR>
    <I>Mon Feb  3 19:37:55 CET 2014</I>
    <P><UL>
        <LI>Previous message: <A HREF="000326.html">[99s-extend] Accept header in POST request
</A></li>
        <LI>Next message: <A HREF="000328.html">[99s-extend] Accept header in POST request
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#327">[ date ]</a>
              <a href="thread.html#327">[ thread ]</a>
              <a href="subject.html#327">[ subject ]</a>
              <a href="author.html#327">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>If Accept is sent and is different than text/html, yes.

This is how HTTP is defined. If the client says it speaks only 
content-type X but you can only reply with content-type Y, you error out 
early and stop processing the request. On the other hand if the client 
doesn't say what content-type it speaks then the server can choose 
whichever one it wants.

On 02/03/2014 07:26 PM, &#321;ukasz Biedrycki wrote:
&gt;<i> My application sends both headers: &#8220;Content-type&#8221; and &#8220;Accept&#8221; header
</I>&gt;<i> using POST method.
</I>&gt;<i>
</I>&gt;<i> For POST rest handler do I have to specify both: content_types_accepted
</I>&gt;<i> and content_types_provided to manage this kind of request?
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i> On Mon, Feb 3, 2014 at 7:23 PM, Lo&#239;c Hoguin &lt;<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>
</I>&gt;<i> &lt;mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>&gt;&gt; wrote:
</I>&gt;<i>
</I>&gt;<i>     The content-type provided is relevant for any response, not just
</I>&gt;<i>     responses to GET requests. It defaults to text/html. If your client
</I>&gt;<i>     doesn't send that content-type, you have to define the callback.
</I>&gt;<i>
</I>&gt;<i>     I notice that the documentation is incorrect about the relevant
</I>&gt;<i>     methods for this callback, I will open a ticket to fix it soon.
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>     On 02/03/2014 07:13 PM, &#321;ukasz Biedrycki wrote:
</I>&gt;<i>
</I>&gt;<i>         Hi,
</I>&gt;<i>         I have a rest handler that accepts POST and PUT requests with
</I>&gt;<i>         &#8220;application/json&#8221; content type.
</I>&gt;<i>
</I>&gt;<i>         I have content_types_accepted function defined as follows:
</I>&gt;<i>
</I>&gt;<i>         content_types_accepted(Req, State) -&gt;
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>         {[{&#8216;application/json', from_json}], Req, State}.
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>         The problem I have is within a request that has two headers:
</I>&gt;<i>
</I>&gt;<i>         *Content-type*: application/json
</I>&gt;<i>         *Accept*: application/json
</I>&gt;<i>
</I>&gt;<i>         With this combination I receive *406*.
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>         You can repeat it with test:
</I>&gt;<i>
</I>&gt;<i>         http_SUITE.erl:
</I>&gt;<i>         1072 rest_postonly(Config) -&gt;
</I>&gt;<i>         1073     Client = ?config(client, Config),
</I>&gt;<i>         1074     Headers = [
</I>&gt;<i>         1075         {&lt;&lt;&quot;content-type&quot;&gt;&gt;, &lt;&lt;&quot;text/plain&quot;&gt;&gt;},
</I>&gt;<i>         1076         {&lt;&lt;&quot;accept&quot;&gt;&gt;, &lt;&lt;&quot;text/plain&quot;&gt;&gt;}
</I>&gt;<i>         1077     ],
</I>&gt;<i>         1078     {ok, Client2} = cowboy_client:request(&lt;&lt;&quot;POST&quot;__&gt;&gt;,
</I>&gt;<i>         1079         build_url(&quot;/postonly&quot;, Config), Headers, &quot;12345&quot;,
</I>&gt;<i>         Client),
</I>&gt;<i>         1080     {ok, 204, _, _} = cowboy_client:response(__Client2).
</I>&gt;<i>
</I>&gt;<i>         My solution to that was to add a content_types_provided function:
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>         content_types_provided(Req, State) -&gt;
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>         ContentTypes = [{{&lt;&lt;&quot;application&quot;&gt;&gt;, &lt;&lt;&quot;json&quot;&gt;&gt;, '*'}, to_json}],
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>         {ContentTypes, Req, State}.
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>         But it is useless as *to_json* callback registered is not called
</I>&gt;<i>         anyhow.
</I>&gt;<i>
</I>&gt;<i>         Adding *content_types_provided* function is a correct solution
</I>&gt;<i>         in this case?
</I>&gt;<i>
</I>&gt;<i>         Or I am missing something here?
</I>&gt;<i>         &#8220;Accept&#8221; header is not relevant only in case of GET requests?
</I>&gt;<i>
</I>&gt;<i>         Thank for help,
</I>&gt;<i>         &#321;ukasz Biedrycki
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>         _________________________________________________
</I>&gt;<i>         Extend mailing list
</I>&gt;<i>         <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A> &lt;mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A>&gt;
</I>&gt;<i>         <A HREF="https://lists.ninenines.eu/__listinfo/extend">https://lists.ninenines.eu/__listinfo/extend</A>
</I>&gt;<i>         &lt;<A HREF="https://lists.ninenines.eu/listinfo/extend">https://lists.ninenines.eu/listinfo/extend</A>&gt;
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>     --
</I>&gt;<i>     Lo&#239;c Hoguin
</I>&gt;<i>     <A HREF="http://ninenines.eu">http://ninenines.eu</A>
</I>&gt;<i>
</I>&gt;<i>
</I>
-- 
Lo&#239;c Hoguin
<A HREF="http://ninenines.eu">http://ninenines.eu</A>

</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="000326.html">[99s-extend] Accept header in POST request
</A></li>
	<LI>Next message: <A HREF="000328.html">[99s-extend] Accept header in POST request
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#327">[ date ]</a>
              <a href="thread.html#327">[ thread ]</a>
              <a href="subject.html#327">[ subject ]</a>
              <a href="author.html#327">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>