diff options
Diffstat (limited to '_build/static/archives/extend/2014-February/000325.html')
| -rw-r--r-- | _build/static/archives/extend/2014-February/000325.html | 134 |
1 files changed, 134 insertions, 0 deletions
diff --git a/_build/static/archives/extend/2014-February/000325.html b/_build/static/archives/extend/2014-February/000325.html new file mode 100644 index 00000000..784e1a10 --- /dev/null +++ b/_build/static/archives/extend/2014-February/000325.html @@ -0,0 +1,134 @@ +<!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=%3C52EFDEA4.6050004%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="000324.html"> + <LINK REL="Next" HREF="000326.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Accept header in POST request</H1> + <B>Loï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=%3C52EFDEA4.6050004%40ninenines.eu%3E" + TITLE="[99s-extend] Accept header in POST request">essen at ninenines.eu + </A><BR> + <I>Mon Feb 3 19:23:32 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000324.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000326.html">[99s-extend] Accept header in POST request +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#325">[ date ]</a> + <a href="thread.html#325">[ thread ]</a> + <a href="subject.html#325">[ subject ]</a> + <a href="author.html#325">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>The content-type provided is relevant for any response, not just +responses to GET requests. It defaults to text/html. If your client +doesn't send that content-type, you have to define the callback. + +I notice that the documentation is incorrect about the relevant methods +for this callback, I will open a ticket to fix it soon. + +On 02/03/2014 07:13 PM, Łukasz Biedrycki wrote: +><i> Hi, +</I>><i> I have a rest handler that accepts POST and PUT requests with +</I>><i> “application/json” content type. +</I>><i> +</I>><i> I have content_types_accepted function defined as follows: +</I>><i> +</I>><i> content_types_accepted(Req, State) -> +</I>><i> +</I>><i> +</I>><i> {[{‘application/json', from_json}], Req, State}. +</I>><i> +</I>><i> +</I>><i> +</I>><i> The problem I have is within a request that has two headers: +</I>><i> +</I>><i> *Content-type*: application/json +</I>><i> *Accept*: application/json +</I>><i> +</I>><i> With this combination I receive *406*. +</I>><i> +</I>><i> You can repeat it with test: +</I>><i> +</I>><i> http_SUITE.erl: +</I>><i> 1072 rest_postonly(Config) -> +</I>><i> 1073 Client = ?config(client, Config), +</I>><i> 1074 Headers = [ +</I>><i> 1075 {<<"content-type">>, <<"text/plain">>}, +</I>><i> 1076 {<<"accept">>, <<"text/plain">>} +</I>><i> 1077 ], +</I>><i> 1078 {ok, Client2} = cowboy_client:request(<<"POST">>, +</I>><i> 1079 build_url("/postonly", Config), Headers, "12345", Client), +</I>><i> 1080 {ok, 204, _, _} = cowboy_client:response(Client2). +</I>><i> +</I>><i> My solution to that was to add a content_types_provided function: +</I>><i> +</I>><i> +</I>><i> content_types_provided(Req, State) -> +</I>><i> +</I>><i> +</I>><i> ContentTypes = [{{<<"application">>, <<"json">>, '*'}, to_json}], +</I>><i> +</I>><i> +</I>><i> {ContentTypes, Req, State}. +</I>><i> +</I>><i> +</I>><i> +</I>><i> But it is useless as *to_json* callback registered is not called anyhow. +</I>><i> +</I>><i> Adding *content_types_provided* function is a correct solution in this case? +</I>><i> Or I am missing something here? +</I>><i> “Accept” header is not relevant only in case of GET requests? +</I>><i> +</I>><i> Thank for help, +</I>><i> Łukasz Biedrycki +</I>><i> +</I>><i> +</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="000324.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000326.html">[99s-extend] Accept header in POST request +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#325">[ date ]</a> + <a href="thread.html#325">[ thread ]</a> + <a href="subject.html#325">[ subject ]</a> + <a href="author.html#325">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> |