diff options
Diffstat (limited to 'archives/extend/2014-February')
21 files changed, 2829 insertions, 0 deletions
diff --git a/archives/extend/2014-February/000324.html b/archives/extend/2014-February/000324.html new file mode 100644 index 00000000..6fc1fc47 --- /dev/null +++ b/archives/extend/2014-February/000324.html @@ -0,0 +1,106 @@ +<!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=%3CCAKfrUsi-hZ-k3QUnhmdRTE1NPZ4j7Lgb2L8xWNdaQ4vk%2Bnw2VA%40mail.gmail.com%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="Next" HREF="000325.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Accept header in POST request</H1> + <B>Łukasz Biedrycki</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Accept%20header%20in%20POST%20request&In-Reply-To=%3CCAKfrUsi-hZ-k3QUnhmdRTE1NPZ4j7Lgb2L8xWNdaQ4vk%2Bnw2VA%40mail.gmail.com%3E" + TITLE="[99s-extend] Accept header in POST request">lukasz.biedrycki at gmail.com + </A><BR> + <I>Mon Feb 3 19:13:04 CET 2014</I> + <P><UL> + + <LI>Next message: <A HREF="000325.html">[99s-extend] Accept header in POST request +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#324">[ date ]</a> + <a href="thread.html#324">[ thread ]</a> + <a href="subject.html#324">[ subject ]</a> + <a href="author.html#324">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, +I have a rest handler that accepts POST and PUT requests with +“application/json” content type. + +I have content_types_accepted function defined as follows: + +content_types_accepted(Req, State) -> + {[{‘application/json', from_json}], Req, State}. + + +The problem I have is within a request that has two headers: + +*Content-type*: application/json +*Accept*: application/json + +With this combination I receive *406*. + +You can repeat it with test: + +http_SUITE.erl: +1072 rest_postonly(Config) -> +1073 Client = ?config(client, Config), +1074 Headers = [ +1075 {<<"content-type">>, <<"text/plain">>}, +1076 {<<"accept">>, <<"text/plain">>} +1077 ], +1078 {ok, Client2} = cowboy_client:request(<<"POST">>, +1079 build_url("/postonly", Config), Headers, "12345", Client), +1080 {ok, 204, _, _} = cowboy_client:response(Client2). + +My solution to that was to add a content_types_provided function: + +content_types_provided(Req, State) -> + ContentTypes = [{{<<"application">>, <<"json">>, '*'}, to_json}], + {ContentTypes, Req, State}. + + +But it is useless as *to_json* callback registered is not called anyhow. + +Adding *content_types_provided* function is a correct solution in this case? +Or I am missing something here? +“Accept” header is not relevant only in case of GET requests? + +Thank for help, +Łukasz Biedrycki +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140203/104f8577/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140203/104f8577/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="000325.html">[99s-extend] Accept header in POST request +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#324">[ date ]</a> + <a href="thread.html#324">[ thread ]</a> + <a href="subject.html#324">[ subject ]</a> + <a href="author.html#324">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000325.html b/archives/extend/2014-February/000325.html new file mode 100644 index 00000000..784e1a10 --- /dev/null +++ b/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> diff --git a/archives/extend/2014-February/000326.html b/archives/extend/2014-February/000326.html new file mode 100644 index 00000000..98ef5924 --- /dev/null +++ b/archives/extend/2014-February/000326.html @@ -0,0 +1,151 @@ +<!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=%3CCAKfrUsiZaAt3k0hDcP2rzUs%3Dw0mTLF7TH3fo%2B9oLbDu7i0sq-g%40mail.gmail.com%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="000325.html"> + <LINK REL="Next" HREF="000327.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Accept header in POST request</H1> + <B>Łukasz Biedrycki</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Accept%20header%20in%20POST%20request&In-Reply-To=%3CCAKfrUsiZaAt3k0hDcP2rzUs%3Dw0mTLF7TH3fo%2B9oLbDu7i0sq-g%40mail.gmail.com%3E" + TITLE="[99s-extend] Accept header in POST request">lukasz.biedrycki at gmail.com + </A><BR> + <I>Mon Feb 3 19:26:17 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000325.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000327.html">[99s-extend] Accept header in POST request +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#326">[ date ]</a> + <a href="thread.html#326">[ thread ]</a> + <a href="subject.html#326">[ subject ]</a> + <a href="author.html#326">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>My application sends both headers: “Content-type” and “Accept” header using +POST method. + +For POST rest handler do I have to specify both: content_types_accepted and +content_types_provided to manage this kind of request? + + +On Mon, Feb 3, 2014 at 7:23 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: + +><i> The content-type provided is relevant for any response, not just responses +</I>><i> to GET requests. It defaults to text/html. If your client doesn't send that +</I>><i> content-type, you have to define the callback. +</I>><i> +</I>><i> I notice that the documentation is incorrect about the relevant methods +</I>><i> for this callback, I will open a ticket to fix it soon. +</I>><i> +</I>><i> +</I>><i> On 02/03/2014 07:13 PM, Łukasz Biedrycki wrote: +</I>><i> +</I>>><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> +</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 +</I>>><i> case? +</I>>><i> +</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>>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I>-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140203/2982cff3/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140203/2982cff3/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000325.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000327.html">[99s-extend] Accept header in POST request +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#326">[ date ]</a> + <a href="thread.html#326">[ thread ]</a> + <a href="subject.html#326">[ subject ]</a> + <a href="author.html#326">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000327.html b/archives/extend/2014-February/000327.html new file mode 100644 index 00000000..d9e2859b --- /dev/null +++ b/archives/extend/2014-February/000327.html @@ -0,0 +1,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ï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, Łukasz Biedrycki wrote: +><i> My application sends both headers: “Content-type” and “Accept” header +</I>><i> using POST method. +</I>><i> +</I>><i> For POST rest handler do I have to specify both: content_types_accepted +</I>><i> and content_types_provided to manage this kind of request? +</I>><i> +</I>><i> +</I>><i> On Mon, Feb 3, 2014 at 7:23 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A> +</I>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>>> wrote: +</I>><i> +</I>><i> The content-type provided is relevant for any response, not just +</I>><i> responses to GET requests. It defaults to text/html. If your client +</I>><i> doesn't send that content-type, you have to define the callback. +</I>><i> +</I>><i> I notice that the documentation is incorrect about the relevant +</I>><i> methods for this callback, I will open a ticket to fix it soon. +</I>><i> +</I>><i> +</I>><i> On 02/03/2014 07:13 PM, Łukasz Biedrycki wrote: +</I>><i> +</I>><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> +</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", +</I>><i> 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 +</I>><i> anyhow. +</I>><i> +</I>><i> Adding *content_types_provided* function is a correct solution +</I>><i> in this case? +</I>><i> +</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> <mailto:<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> <<A HREF="https://lists.ninenines.eu/listinfo/extend">https://lists.ninenines.eu/listinfo/extend</A>> +</I>><i> +</I>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</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="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> diff --git a/archives/extend/2014-February/000328.html b/archives/extend/2014-February/000328.html new file mode 100644 index 00000000..95c2b425 --- /dev/null +++ b/archives/extend/2014-February/000328.html @@ -0,0 +1,195 @@ +<!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=%3CCAKfrUsiHdRRzsBJ_Ns%2Bsw2BdcwbB9dKbx-m6UUL%2BhRj%3D%3DwXY%3DA%40mail.gmail.com%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="000327.html"> + <LINK REL="Next" HREF="000329.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Accept header in POST request</H1> + <B>Łukasz Biedrycki</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Accept%20header%20in%20POST%20request&In-Reply-To=%3CCAKfrUsiHdRRzsBJ_Ns%2Bsw2BdcwbB9dKbx-m6UUL%2BhRj%3D%3DwXY%3DA%40mail.gmail.com%3E" + TITLE="[99s-extend] Accept header in POST request">lukasz.biedrycki at gmail.com + </A><BR> + <I>Mon Feb 3 20:08:12 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000327.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000329.html">[99s-extend] Accept header in POST request +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#328">[ date ]</a> + <a href="thread.html#328">[ thread ]</a> + <a href="subject.html#328">[ subject ]</a> + <a href="author.html#328">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Ok, +it is more clear for me. + +Last question I have is about content_types_provided function. + +Is it safe to define it like this? + +content_types_provided(R, S) -> + ContentTypes = [{{<<"application">>, <<"json">>, '*'}, *undefined*}], + {ContentTypes, Req, State}. + +Callback in content_types_provided is useless for POST requests, as it +won’t be called. +Is it safe to use *undefined *atom, to have a source code clearer? + + + + +On Mon, Feb 3, 2014 at 7:37 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: + +><i> If Accept is sent and is different than text/html, yes. +</I>><i> +</I>><i> This is how HTTP is defined. If the client says it speaks only +</I>><i> content-type X but you can only reply with content-type Y, you error out +</I>><i> early and stop processing the request. On the other hand if the client +</I>><i> doesn't say what content-type it speaks then the server can choose +</I>><i> whichever one it wants. +</I>><i> +</I>><i> +</I>><i> On 02/03/2014 07:26 PM, Łukasz Biedrycki wrote: +</I>><i> +</I>>><i> My application sends both headers: “Content-type” and “Accept” header +</I>>><i> using POST method. +</I>>><i> +</I>>><i> For POST rest handler do I have to specify both: content_types_accepted +</I>>><i> and content_types_provided to manage this kind of request? +</I>>><i> +</I>>><i> +</I>>><i> On Mon, Feb 3, 2014 at 7:23 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A> +</I>>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>>> wrote: +</I>>><i> +</I>>><i> The content-type provided is relevant for any response, not just +</I>>><i> responses to GET requests. It defaults to text/html. If your client +</I>>><i> doesn't send that content-type, you have to define the callback. +</I>>><i> +</I>>><i> I notice that the documentation is incorrect about the relevant +</I>>><i> methods for this callback, I will open a ticket to fix it soon. +</I>>><i> +</I>>><i> +</I>>><i> On 02/03/2014 07:13 PM, Łukasz Biedrycki wrote: +</I>>><i> +</I>>><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> +</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> +</I>>><i> 1079 build_url("/postonly", Config), Headers, "12345", +</I>>><i> Client), +</I>>><i> 1080 {ok, 204, _, _} = cowboy_client:response(__Client2). +</I>>><i> +</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 +</I>>><i> anyhow. +</I>>><i> +</I>>><i> Adding *content_types_provided* function is a correct solution +</I>>><i> in this case? +</I>>><i> +</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> <mailto:<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>>><i> <<A HREF="https://lists.ninenines.eu/listinfo/extend">https://lists.ninenines.eu/listinfo/extend</A>> +</I>>><i> +</I>>><i> +</I>>><i> -- +</I>>><i> Loïc Hoguin +</I>>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>>><i> +</I>>><i> +</I>>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I>-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140203/088e7e6a/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140203/088e7e6a/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000327.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000329.html">[99s-extend] Accept header in POST request +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#328">[ date ]</a> + <a href="thread.html#328">[ thread ]</a> + <a href="subject.html#328">[ subject ]</a> + <a href="author.html#328">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000329.html b/archives/extend/2014-February/000329.html new file mode 100644 index 00000000..7668623a --- /dev/null +++ b/archives/extend/2014-February/000329.html @@ -0,0 +1,223 @@ +<!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=%3C52EFEAE0.7050804%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="000328.html"> + <LINK REL="Next" HREF="000330.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=%3C52EFEAE0.7050804%40ninenines.eu%3E" + TITLE="[99s-extend] Accept header in POST request">essen at ninenines.eu + </A><BR> + <I>Mon Feb 3 20:15:44 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000328.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000330.html">[99s-extend] Accept header in POST request +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#329">[ date ]</a> + <a href="thread.html#329">[ thread ]</a> + <a href="subject.html#329">[ subject ]</a> + <a href="author.html#329">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Sure. It won't be called if not a GET or HEAD request so that's probably +the best value you can return in your case. + +On 02/03/2014 08:08 PM, Łukasz Biedrycki wrote: +><i> Ok, +</I>><i> it is more clear for me. +</I>><i> +</I>><i> Last question I have is about content_types_provided function. +</I>><i> +</I>><i> Is it safe to define it like this? +</I>><i> +</I>><i> content_types_provided(R, S) -> +</I>><i> ContentTypes = [{{<<"application">>, <<"json">>, '*'}, *undefined*}], +</I>><i> {ContentTypes, Req, State}. +</I>><i> +</I>><i> Callback in content_types_provided is useless for POST requests, as it +</I>><i> won’t be called. +</I>><i> Is it safe to use *undefined *atom, to have a source code clearer? +</I>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i> On Mon, Feb 3, 2014 at 7:37 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A> +</I>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>>> wrote: +</I>><i> +</I>><i> If Accept is sent and is different than text/html, yes. +</I>><i> +</I>><i> This is how HTTP is defined. If the client says it speaks only +</I>><i> content-type X but you can only reply with content-type Y, you error +</I>><i> out early and stop processing the request. On the other hand if the +</I>><i> client doesn't say what content-type it speaks then the server can +</I>><i> choose whichever one it wants. +</I>><i> +</I>><i> +</I>><i> On 02/03/2014 07:26 PM, Łukasz Biedrycki wrote: +</I>><i> +</I>><i> My application sends both headers: “Content-type” and “Accept” +</I>><i> header +</I>><i> using POST method. +</I>><i> +</I>><i> For POST rest handler do I have to specify both: +</I>><i> content_types_accepted +</I>><i> and content_types_provided to manage this kind of request? +</I>><i> +</I>><i> +</I>><i> On Mon, Feb 3, 2014 at 7:23 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A> +</I>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> +</I>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>>>> wrote: +</I>><i> +</I>><i> The content-type provided is relevant for any response, not +</I>><i> just +</I>><i> responses to GET requests. It defaults to text/html. If +</I>><i> your client +</I>><i> doesn't send that content-type, you have to define the +</I>><i> callback. +</I>><i> +</I>><i> I notice that the documentation is incorrect about the relevant +</I>><i> methods for this callback, I will open a ticket to fix it soon. +</I>><i> +</I>><i> +</I>><i> On 02/03/2014 07:13 PM, Łukasz Biedrycki wrote: +</I>><i> +</I>><i> Hi, +</I>><i> I have a rest handler that accepts POST and PUT +</I>><i> 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 +</I>><i> 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> +</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} = +</I>><i> cowboy_client:request(<<"POST"____>>, +</I>><i> +</I>><i> 1079 build_url("/postonly", Config), Headers, +</I>><i> "12345", +</I>><i> Client), +</I>><i> 1080 {ok, 204, _, _} = +</I>><i> cowboy_client:response(____Client2). +</I>><i> +</I>><i> +</I>><i> My solution to that was to add a content_types_provided +</I>><i> function: +</I>><i> +</I>><i> +</I>><i> content_types_provided(Req, State) -> +</I>><i> +</I>><i> +</I>><i> ContentTypes = [{{<<"application">>, <<"json">>, '*'}, +</I>><i> 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 +</I>><i> not called +</I>><i> anyhow. +</I>><i> +</I>><i> Adding *content_types_provided* function is a correct +</I>><i> solution +</I>><i> in this case? +</I>><i> +</I>><i> Or I am missing something here? +</I>><i> “Accept” header is not relevant only in case of GET +</I>><i> 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> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A>> +</I>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.__ninenines.eu</A> +</I>><i> <mailto:<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> <<A HREF="https://lists.ninenines.eu/__listinfo/extend">https://lists.ninenines.eu/__listinfo/extend</A>> +</I>><i> +</I>><i> <<A HREF="https://lists.ninenines.eu/__listinfo/extend">https://lists.ninenines.eu/__listinfo/extend</A> +</I>><i> <<A HREF="https://lists.ninenines.eu/listinfo/extend">https://lists.ninenines.eu/listinfo/extend</A>>> +</I>><i> +</I>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I>><i> +</I>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</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="000328.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000330.html">[99s-extend] Accept header in POST request +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#329">[ date ]</a> + <a href="thread.html#329">[ thread ]</a> + <a href="subject.html#329">[ subject ]</a> + <a href="author.html#329">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000330.html b/archives/extend/2014-February/000330.html new file mode 100644 index 00000000..dcc28287 --- /dev/null +++ b/archives/extend/2014-February/000330.html @@ -0,0 +1,244 @@ +<!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=%3CCAKfrUsjrQxO_6CB0Hw85aqcWe%2BC5j0Dv%2BcNbK7ffSzv7npMvMA%40mail.gmail.com%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="000329.html"> + <LINK REL="Next" HREF="000331.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Accept header in POST request</H1> + <B>Łukasz Biedrycki</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Accept%20header%20in%20POST%20request&In-Reply-To=%3CCAKfrUsjrQxO_6CB0Hw85aqcWe%2BC5j0Dv%2BcNbK7ffSzv7npMvMA%40mail.gmail.com%3E" + TITLE="[99s-extend] Accept header in POST request">lukasz.biedrycki at gmail.com + </A><BR> + <I>Mon Feb 3 20:16:29 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000329.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000331.html">[99s-extend] Metrics per request and handler +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#330">[ date ]</a> + <a href="thread.html#330">[ thread ]</a> + <a href="subject.html#330">[ subject ]</a> + <a href="author.html#330">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Perfect, thanks a lot! +Cheers, +Ł. + + +On Mon, Feb 3, 2014 at 8:15 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: + +><i> Sure. It won't be called if not a GET or HEAD request so that's probably +</I>><i> the best value you can return in your case. +</I>><i> +</I>><i> +</I>><i> On 02/03/2014 08:08 PM, Łukasz Biedrycki wrote: +</I>><i> +</I>>><i> Ok, +</I>>><i> it is more clear for me. +</I>>><i> +</I>>><i> Last question I have is about content_types_provided function. +</I>>><i> +</I>>><i> Is it safe to define it like this? +</I>>><i> +</I>>><i> content_types_provided(R, S) -> +</I>>><i> ContentTypes = [{{<<"application">>, <<"json">>, '*'}, *undefined*}], +</I>>><i> +</I>>><i> {ContentTypes, Req, State}. +</I>>><i> +</I>>><i> Callback in content_types_provided is useless for POST requests, as it +</I>>><i> won’t be called. +</I>>><i> Is it safe to use *undefined *atom, to have a source code clearer? +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> On Mon, Feb 3, 2014 at 7:37 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A> +</I>>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>>> wrote: +</I>>><i> +</I>>><i> If Accept is sent and is different than text/html, yes. +</I>>><i> +</I>>><i> This is how HTTP is defined. If the client says it speaks only +</I>>><i> content-type X but you can only reply with content-type Y, you error +</I>>><i> out early and stop processing the request. On the other hand if the +</I>>><i> client doesn't say what content-type it speaks then the server can +</I>>><i> choose whichever one it wants. +</I>>><i> +</I>>><i> +</I>>><i> On 02/03/2014 07:26 PM, Łukasz Biedrycki wrote: +</I>>><i> +</I>>><i> My application sends both headers: “Content-type” and “Accept” +</I>>><i> header +</I>>><i> using POST method. +</I>>><i> +</I>>><i> For POST rest handler do I have to specify both: +</I>>><i> content_types_accepted +</I>>><i> and content_types_provided to manage this kind of request? +</I>>><i> +</I>>><i> +</I>>><i> On Mon, Feb 3, 2014 at 7:23 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A> +</I>>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> +</I>>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>>>> wrote: +</I>>><i> +</I>>><i> The content-type provided is relevant for any response, not +</I>>><i> just +</I>>><i> responses to GET requests. It defaults to text/html. If +</I>>><i> your client +</I>>><i> doesn't send that content-type, you have to define the +</I>>><i> callback. +</I>>><i> +</I>>><i> I notice that the documentation is incorrect about the +</I>>><i> relevant +</I>>><i> methods for this callback, I will open a ticket to fix it +</I>>><i> soon. +</I>>><i> +</I>>><i> +</I>>><i> On 02/03/2014 07:13 PM, Łukasz Biedrycki wrote: +</I>>><i> +</I>>><i> Hi, +</I>>><i> I have a rest handler that accepts POST and PUT +</I>>><i> requests with +</I>>><i> “application/json” content type. +</I>>><i> +</I>>><i> I have content_types_accepted function defined as +</I>>><i> 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 +</I>>><i> 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> +</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} = +</I>>><i> cowboy_client:request(<<"POST"____>>, +</I>>><i> +</I>>><i> +</I>>><i> 1079 build_url("/postonly", Config), Headers, +</I>>><i> "12345", +</I>>><i> Client), +</I>>><i> 1080 {ok, 204, _, _} = +</I>>><i> cowboy_client:response(____Client2). +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> My solution to that was to add a content_types_provided +</I>>><i> function: +</I>>><i> +</I>>><i> +</I>>><i> content_types_provided(Req, State) -> +</I>>><i> +</I>>><i> +</I>>><i> ContentTypes = [{{<<"application">>, <<"json">>, '*'}, +</I>>><i> 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 +</I>>><i> not called +</I>>><i> anyhow. +</I>>><i> +</I>>><i> Adding *content_types_provided* function is a correct +</I>>><i> solution +</I>>><i> in this case? +</I>>><i> +</I>>><i> Or I am missing something here? +</I>>><i> “Accept” header is not relevant only in case of GET +</I>>><i> requests? +</I>>><i> +</I>>><i> Thank for help, +</I>>><i> Łukasz Biedrycki +</I>>><i> +</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> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A>> +</I>>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.__ninenines.eu</A> +</I>>><i> <mailto:<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> <<A HREF="https://lists.ninenines.eu/__listinfo/extend">https://lists.ninenines.eu/__listinfo/extend</A>> +</I>>><i> +</I>>><i> +</I>>><i> <<A HREF="https://lists.ninenines.eu/__listinfo/extend">https://lists.ninenines.eu/__listinfo/extend</A> +</I>>><i> <<A HREF="https://lists.ninenines.eu/listinfo/extend">https://lists.ninenines.eu/listinfo/extend</A>>> +</I>>><i> +</I>>><i> +</I>>><i> -- +</I>>><i> Loïc Hoguin +</I>>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> -- +</I>>><i> Loïc Hoguin +</I>>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>>><i> +</I>>><i> +</I>>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I>-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140203/e84f6223/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140203/e84f6223/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000329.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000331.html">[99s-extend] Metrics per request and handler +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#330">[ date ]</a> + <a href="thread.html#330">[ thread ]</a> + <a href="subject.html#330">[ subject ]</a> + <a href="author.html#330">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000331.html b/archives/extend/2014-February/000331.html new file mode 100644 index 00000000..d8ce154e --- /dev/null +++ b/archives/extend/2014-February/000331.html @@ -0,0 +1,79 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Metrics per request and handler + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Metrics%20per%20request%20and%20handler&In-Reply-To=%3CCAKfrUsikVjhGk%2BM8L%3D9gSxwdmTBtyn1shXsFe35L%2B6eHZYCwyA%40mail.gmail.com%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="000330.html"> + <LINK REL="Next" HREF="000332.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Metrics per request and handler</H1> + <B>Łukasz Biedrycki</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Metrics%20per%20request%20and%20handler&In-Reply-To=%3CCAKfrUsikVjhGk%2BM8L%3D9gSxwdmTBtyn1shXsFe35L%2B6eHZYCwyA%40mail.gmail.com%3E" + TITLE="[99s-extend] Metrics per request and handler">lukasz.biedrycki at gmail.com + </A><BR> + <I>Fri Feb 7 17:56:26 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000330.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000332.html">[99s-extend] Metrics per request and handler +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#331">[ date ]</a> + <a href="thread.html#331">[ thread ]</a> + <a href="subject.html#331">[ subject ]</a> + <a href="author.html#331">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, +in my application I would like to add some metrics per handler and per +response http status code. + +One way is to add on response callback function, but there I do not have an +information about handler and handler opts. + +Second way is to add a middleware, but then I do not have an information +about response status code. + +Frankly, I like second way more. +How do like an idea to add response status code to request record similar +to: resp_headers or resp_body ? + +Cheers, +Łukasz Biedrycki +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140207/904cc7bf/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140207/904cc7bf/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000330.html">[99s-extend] Accept header in POST request +</A></li> + <LI>Next message: <A HREF="000332.html">[99s-extend] Metrics per request and handler +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#331">[ date ]</a> + <a href="thread.html#331">[ thread ]</a> + <a href="subject.html#331">[ subject ]</a> + <a href="author.html#331">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000332.html b/archives/extend/2014-February/000332.html new file mode 100644 index 00000000..544ef82c --- /dev/null +++ b/archives/extend/2014-February/000332.html @@ -0,0 +1,94 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Metrics per request and handler + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Metrics%20per%20request%20and%20handler&In-Reply-To=%3CCAKfrUsiqvYuNVW9H0x4xuarorkCHsw5HJaJWasJvd6XgRfAw4g%40mail.gmail.com%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="000331.html"> + <LINK REL="Next" HREF="000333.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Metrics per request and handler</H1> + <B>Łukasz Biedrycki</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Metrics%20per%20request%20and%20handler&In-Reply-To=%3CCAKfrUsiqvYuNVW9H0x4xuarorkCHsw5HJaJWasJvd6XgRfAw4g%40mail.gmail.com%3E" + TITLE="[99s-extend] Metrics per request and handler">lukasz.biedrycki at gmail.com + </A><BR> + <I>Mon Feb 10 10:41:13 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000331.html">[99s-extend] Metrics per request and handler +</A></li> + <LI>Next message: <A HREF="000333.html">[99s-extend] Metrics per request and handler +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#332">[ date ]</a> + <a href="thread.html#332">[ thread ]</a> + <a href="subject.html#332">[ subject ]</a> + <a href="author.html#332">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi again, +another idea is to make environment (Env), which is passed between +middlewares, a part of Request record, so I could have an access to it in +onresponse callback. + +Any of that makes sense? + +Cheers, +Łukasz Biedrycki + + +On Fri, Feb 7, 2014 at 5:56 PM, Łukasz Biedrycki <<A HREF="https://lists.ninenines.eu/listinfo/extend">lukasz.biedrycki at gmail.com</A> +><i> wrote: +</I> +><i> Hi, +</I>><i> in my application I would like to add some metrics per handler and per +</I>><i> response http status code. +</I>><i> +</I>><i> One way is to add on response callback function, but there I do not have +</I>><i> an information about handler and handler opts. +</I>><i> +</I>><i> Second way is to add a middleware, but then I do not have an information +</I>><i> about response status code. +</I>><i> +</I>><i> Frankly, I like second way more. +</I>><i> How do like an idea to add response status code to request record similar +</I>><i> to: resp_headers or resp_body ? +</I>><i> +</I>><i> Cheers, +</I>><i> Łukasz Biedrycki +</I>><i> +</I>-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140210/b46e2bab/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140210/b46e2bab/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000331.html">[99s-extend] Metrics per request and handler +</A></li> + <LI>Next message: <A HREF="000333.html">[99s-extend] Metrics per request and handler +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#332">[ date ]</a> + <a href="thread.html#332">[ thread ]</a> + <a href="subject.html#332">[ subject ]</a> + <a href="author.html#332">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000333.html b/archives/extend/2014-February/000333.html new file mode 100644 index 00000000..3d277eba --- /dev/null +++ b/archives/extend/2014-February/000333.html @@ -0,0 +1,108 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Metrics per request and handler + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Metrics%20per%20request%20and%20handler&In-Reply-To=%3C52F8A0A4.8030109%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="000332.html"> + <LINK REL="Next" HREF="000334.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Metrics per request and handler</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Metrics%20per%20request%20and%20handler&In-Reply-To=%3C52F8A0A4.8030109%40ninenines.eu%3E" + TITLE="[99s-extend] Metrics per request and handler">essen at ninenines.eu + </A><BR> + <I>Mon Feb 10 10:49:24 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000332.html">[99s-extend] Metrics per request and handler +</A></li> + <LI>Next message: <A HREF="000334.html">[99s-extend] Metrics per request and handler +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#333">[ date ]</a> + <a href="thread.html#333">[ thread ]</a> + <a href="subject.html#333">[ subject ]</a> + <a href="author.html#333">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>You have the meta values in Req which are passed everywhere. You can +easily set and retrieve them. + +On 02/10/2014 10:41 AM, Łukasz Biedrycki wrote: +><i> Hi again, +</I>><i> another idea is to make environment (Env), which is passed between +</I>><i> middlewares, a part of Request record, so I could have an access to it in +</I>><i> onresponse callback. +</I>><i> +</I>><i> Any of that makes sense? +</I>><i> +</I>><i> Cheers, +</I>><i> Łukasz Biedrycki +</I>><i> +</I>><i> +</I>><i> On Fri, Feb 7, 2014 at 5:56 PM, Łukasz Biedrycki <<A HREF="https://lists.ninenines.eu/listinfo/extend">lukasz.biedrycki at gmail.com</A> +</I>>><i> wrote: +</I>><i> +</I>>><i> Hi, +</I>>><i> in my application I would like to add some metrics per handler and per +</I>>><i> response http status code. +</I>>><i> +</I>>><i> One way is to add on response callback function, but there I do not have +</I>>><i> an information about handler and handler opts. +</I>>><i> +</I>>><i> Second way is to add a middleware, but then I do not have an information +</I>>><i> about response status code. +</I>>><i> +</I>>><i> Frankly, I like second way more. +</I>>><i> How do like an idea to add response status code to request record similar +</I>>><i> to: resp_headers or resp_body ? +</I>>><i> +</I>>><i> Cheers, +</I>>><i> Łukasz Biedrycki +</I>>><i> +</I>><i> +</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="000332.html">[99s-extend] Metrics per request and handler +</A></li> + <LI>Next message: <A HREF="000334.html">[99s-extend] Metrics per request and handler +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#333">[ date ]</a> + <a href="thread.html#333">[ thread ]</a> + <a href="subject.html#333">[ subject ]</a> + <a href="author.html#333">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000334.html b/archives/extend/2014-February/000334.html new file mode 100644 index 00000000..8f3b0da7 --- /dev/null +++ b/archives/extend/2014-February/000334.html @@ -0,0 +1,127 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Metrics per request and handler + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Metrics%20per%20request%20and%20handler&In-Reply-To=%3CCAKfrUsiCSXx5BTHNHx%3DnkzS5n2EgKVFt-23tz-GX1cV-2Fk_WA%40mail.gmail.com%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="000333.html"> + <LINK REL="Next" HREF="000335.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Metrics per request and handler</H1> + <B>Łukasz Biedrycki</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Metrics%20per%20request%20and%20handler&In-Reply-To=%3CCAKfrUsiCSXx5BTHNHx%3DnkzS5n2EgKVFt-23tz-GX1cV-2Fk_WA%40mail.gmail.com%3E" + TITLE="[99s-extend] Metrics per request and handler">lukasz.biedrycki at gmail.com + </A><BR> + <I>Mon Feb 10 10:51:50 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000333.html">[99s-extend] Metrics per request and handler +</A></li> + <LI>Next message: <A HREF="000335.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#334">[ date ]</a> + <a href="thread.html#334">[ thread ]</a> + <a href="subject.html#334">[ subject ]</a> + <a href="author.html#334">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hey, +I didn’t know about that. +That is exactly what I need! +Thank you! + +Cheers, +Łukasz Biedrycki + + +On Mon, Feb 10, 2014 at 10:49 AM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: + +><i> You have the meta values in Req which are passed everywhere. You can +</I>><i> easily set and retrieve them. +</I>><i> +</I>><i> +</I>><i> On 02/10/2014 10:41 AM, Łukasz Biedrycki wrote: +</I>><i> +</I>>><i> Hi again, +</I>>><i> another idea is to make environment (Env), which is passed between +</I>>><i> middlewares, a part of Request record, so I could have an access to it in +</I>>><i> onresponse callback. +</I>>><i> +</I>>><i> Any of that makes sense? +</I>>><i> +</I>>><i> Cheers, +</I>>><i> Łukasz Biedrycki +</I>>><i> +</I>>><i> +</I>>><i> On Fri, Feb 7, 2014 at 5:56 PM, Łukasz Biedrycki < +</I>>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">lukasz.biedrycki at gmail.com</A> +</I>>><i> +</I>>>><i> wrote: +</I>>>><i> +</I>>><i> +</I>>><i> Hi, +</I>>>><i> in my application I would like to add some metrics per handler and per +</I>>>><i> response http status code. +</I>>>><i> +</I>>>><i> One way is to add on response callback function, but there I do not have +</I>>>><i> an information about handler and handler opts. +</I>>>><i> +</I>>>><i> Second way is to add a middleware, but then I do not have an information +</I>>>><i> about response status code. +</I>>>><i> +</I>>>><i> Frankly, I like second way more. +</I>>>><i> How do like an idea to add response status code to request record similar +</I>>>><i> to: resp_headers or resp_body ? +</I>>>><i> +</I>>>><i> Cheers, +</I>>>><i> Łukasz Biedrycki +</I>>>><i> +</I>>>><i> +</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>>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I>-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140210/bf26d573/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140210/bf26d573/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000333.html">[99s-extend] Metrics per request and handler +</A></li> + <LI>Next message: <A HREF="000335.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#334">[ date ]</a> + <a href="thread.html#334">[ thread ]</a> + <a href="subject.html#334">[ subject ]</a> + <a href="author.html#334">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000335.html b/archives/extend/2014-February/000335.html new file mode 100644 index 00000000..7a2434df --- /dev/null +++ b/archives/extend/2014-February/000335.html @@ -0,0 +1,74 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] do not treat warnings as errors on make? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20do%20not%20treat%20warnings%20as%20errors%20on%20make%3F&In-Reply-To=%3CCAD9h6NH%3DRD9qbU%3Dfu1AG27P0qDCcYpNGcYMaYVSz%2B1DK1WaLQQ%40mail.gmail.com%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="000334.html"> + <LINK REL="Next" HREF="000336.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] do not treat warnings as errors on make?</H1> + <B>Anton Koval'</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20do%20not%20treat%20warnings%20as%20errors%20on%20make%3F&In-Reply-To=%3CCAD9h6NH%3DRD9qbU%3Dfu1AG27P0qDCcYpNGcYMaYVSz%2B1DK1WaLQQ%40mail.gmail.com%3E" + TITLE="[99s-extend] do not treat warnings as errors on make?">psihonavt at gmail.com + </A><BR> + <I>Mon Feb 10 19:44:54 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000334.html">[99s-extend] Metrics per request and handler +</A></li> + <LI>Next message: <A HREF="000336.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#335">[ date ]</a> + <a href="thread.html#335">[ thread ]</a> + <a href="subject.html#335">[ subject ]</a> + <a href="author.html#335">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello, + +as I understand, by default `make all` performs compile with option +warnings_as_errors. How can I disable this option? +There are options described at +<A HREF="https://github.com/extend/erlang.mk#optionsand">https://github.com/extend/erlang.mk#optionsand</A> I believe that +ERLC_OPTS +should be filled with `-warnings_as_errors`. But it is unclear for me where +have I to add(put) that option? + +Thanks. +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140210/a2b35e2f/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140210/a2b35e2f/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000334.html">[99s-extend] Metrics per request and handler +</A></li> + <LI>Next message: <A HREF="000336.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#335">[ date ]</a> + <a href="thread.html#335">[ thread ]</a> + <a href="subject.html#335">[ subject ]</a> + <a href="author.html#335">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000336.html b/archives/extend/2014-February/000336.html new file mode 100644 index 00000000..b3ce26a4 --- /dev/null +++ b/archives/extend/2014-February/000336.html @@ -0,0 +1,87 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] do not treat warnings as errors on make? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20do%20not%20treat%20warnings%20as%20errors%20on%20make%3F&In-Reply-To=%3C52F91EE1.7040809%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="000335.html"> + <LINK REL="Next" HREF="000337.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] do not treat warnings as errors on make?</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20do%20not%20treat%20warnings%20as%20errors%20on%20make%3F&In-Reply-To=%3C52F91EE1.7040809%40ninenines.eu%3E" + TITLE="[99s-extend] do not treat warnings as errors on make?">essen at ninenines.eu + </A><BR> + <I>Mon Feb 10 19:48:01 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000335.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI>Next message: <A HREF="000337.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#336">[ date ]</a> + <a href="thread.html#336">[ thread ]</a> + <a href="subject.html#336">[ subject ]</a> + <a href="author.html#336">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>You can just define ERLC_OPTS before you include erlang.mk and it'll use +that instead. I'm not sure why you want to disable that though, warnings +usually alert you of bugs in your code. + +On 02/10/2014 07:44 PM, Anton Koval' wrote: +><i> Hello, +</I>><i> +</I>><i> as I understand, by default `make all` performs compile with +</I>><i> option**warnings_as_errors.**How can I disable this option? +</I>><i> There are options described at +</I>><i> <A HREF="https://github.com/extend/erlang.mk#options">https://github.com/extend/erlang.mk#options</A> and I believe that +</I>><i> |ERLC_OPTS should be filled with `-|warnings_as_errors`**. But it is +</I>><i> unclear for me where have I to add(put) that option? +</I>><i> +</I>><i> Thanks. +</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="000335.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI>Next message: <A HREF="000337.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#336">[ date ]</a> + <a href="thread.html#336">[ thread ]</a> + <a href="subject.html#336">[ subject ]</a> + <a href="author.html#336">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000337.html b/archives/extend/2014-February/000337.html new file mode 100644 index 00000000..bb16e835 --- /dev/null +++ b/archives/extend/2014-February/000337.html @@ -0,0 +1,103 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] do not treat warnings as errors on make? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20do%20not%20treat%20warnings%20as%20errors%20on%20make%3F&In-Reply-To=%3CCAD9h6NEzSej%3D2OAfPcksSbBuk-2ui1P5ipaCgB0sQKeNt4Zddw%40mail.gmail.com%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="000336.html"> + <LINK REL="Next" HREF="000338.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] do not treat warnings as errors on make?</H1> + <B>Anton Koval'</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20do%20not%20treat%20warnings%20as%20errors%20on%20make%3F&In-Reply-To=%3CCAD9h6NEzSej%3D2OAfPcksSbBuk-2ui1P5ipaCgB0sQKeNt4Zddw%40mail.gmail.com%3E" + TITLE="[99s-extend] do not treat warnings as errors on make?">psihonavt at gmail.com + </A><BR> + <I>Mon Feb 10 20:22:49 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000336.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI>Next message: <A HREF="000338.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#337">[ date ]</a> + <a href="thread.html#337">[ thread ]</a> + <a href="subject.html#337">[ subject ]</a> + <a href="author.html#337">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thanks for explanation. +My situation: I'm developing some stuff in module. That module in some kind +of "draft' state (e.g. some functions are unused), but regardless that I +want to compile project in order to test some specific parts of that +module. + + +On Mon, Feb 10, 2014 at 8:48 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: + +><i> You can just define ERLC_OPTS before you include erlang.mk and it'll use +</I>><i> that instead. I'm not sure why you want to disable that though, warnings +</I>><i> usually alert you of bugs in your code. +</I>><i> +</I>><i> +</I>><i> On 02/10/2014 07:44 PM, Anton Koval' wrote: +</I>><i> +</I>>><i> Hello, +</I>>><i> +</I>>><i> as I understand, by default `make all` performs compile with +</I>>><i> option**warnings_as_errors.**How can I disable this option? +</I>>><i> +</I>>><i> There are options described at +</I>>><i> <A HREF="https://github.com/extend/erlang.mk#options">https://github.com/extend/erlang.mk#options</A> and I believe that +</I>>><i> |ERLC_OPTS should be filled with `-|warnings_as_errors`**. But it is +</I>>><i> +</I>>><i> unclear for me where have I to add(put) that option? +</I>>><i> +</I>>><i> Thanks. +</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>>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I>-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140210/2ae635a6/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140210/2ae635a6/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000336.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI>Next message: <A HREF="000338.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#337">[ date ]</a> + <a href="thread.html#337">[ thread ]</a> + <a href="subject.html#337">[ subject ]</a> + <a href="author.html#337">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000338.html b/archives/extend/2014-February/000338.html new file mode 100644 index 00000000..a6d41866 --- /dev/null +++ b/archives/extend/2014-February/000338.html @@ -0,0 +1,109 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] do not treat warnings as errors on make? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20do%20not%20treat%20warnings%20as%20errors%20on%20make%3F&In-Reply-To=%3C2424F399-12CA-455D-ACEE-45882873B1D4%40llaisdy.com%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="000337.html"> + <LINK REL="Next" HREF="000339.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] do not treat warnings as errors on make?</H1> + <B>Ivan Uemlianin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20do%20not%20treat%20warnings%20as%20errors%20on%20make%3F&In-Reply-To=%3C2424F399-12CA-455D-ACEE-45882873B1D4%40llaisdy.com%3E" + TITLE="[99s-extend] do not treat warnings as errors on make?">ivan at llaisdy.com + </A><BR> + <I>Mon Feb 10 20:46:54 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000337.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI>Next message: <A HREF="000339.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#338">[ date ]</a> + <a href="thread.html#338">[ thread ]</a> + <a href="subject.html#338">[ subject ]</a> + <a href="author.html#338">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>I promise you, improving the code now to get rid of the warnings is worth it. + +Ivan + +-- +festina lente + + +><i> On 10 Feb 2014, at 19:22, "Anton Koval'" <<A HREF="https://lists.ninenines.eu/listinfo/extend">psihonavt at gmail.com</A>> wrote: +</I>><i> +</I>><i> Thanks for explanation. +</I>><i> My situation: I'm developing some stuff in module. That module in some kind of "draft' state (e.g. some functions are unused), but regardless that I want to compile project in order to test some specific parts of that module. +</I>><i> +</I>><i> +</I>>><i> On Mon, Feb 10, 2014 at 8:48 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: +</I>>><i> You can just define ERLC_OPTS before you include erlang.mk and it'll use that instead. I'm not sure why you want to disable that though, warnings usually alert you of bugs in your code. +</I>>><i> +</I>>><i> +</I>>>><i> On 02/10/2014 07:44 PM, Anton Koval' wrote: +</I>>>><i> Hello, +</I>>>><i> +</I>>>><i> as I understand, by default `make all` performs compile with +</I>>>><i> option**warnings_as_errors.**How can I disable this option? +</I>>>><i> +</I>>>><i> There are options described at +</I>>>><i> <A HREF="https://github.com/extend/erlang.mk#options">https://github.com/extend/erlang.mk#options</A> and I believe that +</I>>>><i> |ERLC_OPTS should be filled with `-|warnings_as_errors`**. But it is +</I>>>><i> +</I>>>><i> unclear for me where have I to add(put) that option? +</I>>>><i> +</I>>>><i> Thanks. +</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>>><i> -- +</I>>><i> Loïc Hoguin +</I>>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</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>-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140210/1781c9d2/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140210/1781c9d2/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000337.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI>Next message: <A HREF="000339.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#338">[ date ]</a> + <a href="thread.html#338">[ thread ]</a> + <a href="subject.html#338">[ subject ]</a> + <a href="author.html#338">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/000339.html b/archives/extend/2014-February/000339.html new file mode 100644 index 00000000..35469a91 --- /dev/null +++ b/archives/extend/2014-February/000339.html @@ -0,0 +1,125 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] do not treat warnings as errors on make? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20do%20not%20treat%20warnings%20as%20errors%20on%20make%3F&In-Reply-To=%3CCAD9h6NE5HaNe7-RUUVQehkWGF9uwmLzhTh_J%3DB6mB9ATyPJumQ%40mail.gmail.com%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="000338.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] do not treat warnings as errors on make?</H1> + <B>Anton Koval'</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20do%20not%20treat%20warnings%20as%20errors%20on%20make%3F&In-Reply-To=%3CCAD9h6NE5HaNe7-RUUVQehkWGF9uwmLzhTh_J%3DB6mB9ATyPJumQ%40mail.gmail.com%3E" + TITLE="[99s-extend] do not treat warnings as errors on make?">psihonavt at gmail.com + </A><BR> + <I>Mon Feb 10 20:55:24 CET 2014</I> + <P><UL> + <LI>Previous message: <A HREF="000338.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#339">[ date ]</a> + <a href="thread.html#339">[ thread ]</a> + <a href="subject.html#339">[ subject ]</a> + <a href="author.html#339">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Got it! :) +fixed all warnings and removed ERLC_OPTS from Makefile. + + +On Mon, Feb 10, 2014 at 9:46 PM, Ivan Uemlianin <<A HREF="https://lists.ninenines.eu/listinfo/extend">ivan at llaisdy.com</A>> wrote: + +><i> I promise you, improving the code now to get rid of the warnings is worth +</I>><i> it. +</I>><i> +</I>><i> Ivan +</I>><i> +</I>><i> -- +</I>><i> festina lente +</I>><i> +</I>><i> +</I>><i> On 10 Feb 2014, at 19:22, "Anton Koval'" <<A HREF="https://lists.ninenines.eu/listinfo/extend">psihonavt at gmail.com</A>> wrote: +</I>><i> +</I>><i> Thanks for explanation. +</I>><i> My situation: I'm developing some stuff in module. That module in some +</I>><i> kind of "draft' state (e.g. some functions are unused), but regardless that +</I>><i> I want to compile project in order to test some specific parts of that +</I>><i> module. +</I>><i> +</I>><i> +</I>><i> On Mon, Feb 10, 2014 at 8:48 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: +</I>><i> +</I>>><i> You can just define ERLC_OPTS before you include erlang.mk and it'll use +</I>>><i> that instead. I'm not sure why you want to disable that though, warnings +</I>>><i> usually alert you of bugs in your code. +</I>>><i> +</I>>><i> +</I>>><i> On 02/10/2014 07:44 PM, Anton Koval' wrote: +</I>>><i> +</I>>>><i> Hello, +</I>>>><i> +</I>>>><i> as I understand, by default `make all` performs compile with +</I>>>><i> option**warnings_as_errors.**How can I disable this option? +</I>>>><i> +</I>>>><i> There are options described at +</I>>>><i> <A HREF="https://github.com/extend/erlang.mk#options">https://github.com/extend/erlang.mk#options</A> and I believe that +</I>>>><i> |ERLC_OPTS should be filled with `-|warnings_as_errors`**. But it is +</I>>>><i> +</I>>>><i> unclear for me where have I to add(put) that option? +</I>>>><i> +</I>>>><i> Thanks. +</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>>>><i> +</I>>><i> -- +</I>>><i> Loïc Hoguin +</I>>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</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>><i> +</I>-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20140210/fa72e2ba/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20140210/fa72e2ba/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000338.html">[99s-extend] do not treat warnings as errors on make? +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#339">[ date ]</a> + <a href="thread.html#339">[ thread ]</a> + <a href="subject.html#339">[ subject ]</a> + <a href="author.html#339">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> diff --git a/archives/extend/2014-February/author.html b/archives/extend/2014-February/author.html new file mode 100644 index 00000000..374894cd --- /dev/null +++ b/archives/extend/2014-February/author.html @@ -0,0 +1,127 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <title>The Extend February 2014 Archive by author</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>February 2014 Archives by author</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://lists.ninenines.eu/listinfo/extend">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Mon Feb 3 19:13:04 CET 2014</i><br> + <b>Ending:</b> <i>Mon Feb 10 20:55:24 CET 2014</i><br> + <b>Messages:</b> 16<p> + <ul> + +<LI><A HREF="000324.html">[99s-extend] Accept header in POST request +</A><A NAME="324"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000326.html">[99s-extend] Accept header in POST request +</A><A NAME="326"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000328.html">[99s-extend] Accept header in POST request +</A><A NAME="328"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000330.html">[99s-extend] Accept header in POST request +</A><A NAME="330"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000331.html">[99s-extend] Metrics per request and handler +</A><A NAME="331"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000332.html">[99s-extend] Metrics per request and handler +</A><A NAME="332"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000334.html">[99s-extend] Metrics per request and handler +</A><A NAME="334"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000325.html">[99s-extend] Accept header in POST request +</A><A NAME="325"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000327.html">[99s-extend] Accept header in POST request +</A><A NAME="327"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000329.html">[99s-extend] Accept header in POST request +</A><A NAME="329"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000333.html">[99s-extend] Metrics per request and handler +</A><A NAME="333"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000336.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="336"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000335.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="335"> </A> +<I>Anton Koval' +</I> + +<LI><A HREF="000337.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="337"> </A> +<I>Anton Koval' +</I> + +<LI><A HREF="000339.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="339"> </A> +<I>Anton Koval' +</I> + +<LI><A HREF="000338.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="338"> </A> +<I>Ivan Uemlianin +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Mon Feb 10 20:55:24 CET 2014</i><br> + <b>Archived on:</b> <i>Wed May 28 18:41:47 CEST 2014</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://lists.ninenines.eu/listinfo/extend">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/archives/extend/2014-February/date.html b/archives/extend/2014-February/date.html new file mode 100644 index 00000000..156b37ba --- /dev/null +++ b/archives/extend/2014-February/date.html @@ -0,0 +1,127 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <title>The Extend February 2014 Archive by date</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>February 2014 Archives by date</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + + <li><b><a href="https://lists.ninenines.eu/listinfo/extend">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Mon Feb 3 19:13:04 CET 2014</i><br> + <b>Ending:</b> <i>Mon Feb 10 20:55:24 CET 2014</i><br> + <b>Messages:</b> 16<p> + <ul> + +<LI><A HREF="000324.html">[99s-extend] Accept header in POST request +</A><A NAME="324"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000325.html">[99s-extend] Accept header in POST request +</A><A NAME="325"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000326.html">[99s-extend] Accept header in POST request +</A><A NAME="326"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000327.html">[99s-extend] Accept header in POST request +</A><A NAME="327"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000328.html">[99s-extend] Accept header in POST request +</A><A NAME="328"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000329.html">[99s-extend] Accept header in POST request +</A><A NAME="329"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000330.html">[99s-extend] Accept header in POST request +</A><A NAME="330"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000331.html">[99s-extend] Metrics per request and handler +</A><A NAME="331"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000332.html">[99s-extend] Metrics per request and handler +</A><A NAME="332"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000333.html">[99s-extend] Metrics per request and handler +</A><A NAME="333"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000334.html">[99s-extend] Metrics per request and handler +</A><A NAME="334"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000335.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="335"> </A> +<I>Anton Koval' +</I> + +<LI><A HREF="000336.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="336"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000337.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="337"> </A> +<I>Anton Koval' +</I> + +<LI><A HREF="000338.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="338"> </A> +<I>Ivan Uemlianin +</I> + +<LI><A HREF="000339.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="339"> </A> +<I>Anton Koval' +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Mon Feb 10 20:55:24 CET 2014</i><br> + <b>Archived on:</b> <i>Wed May 28 18:41:47 CEST 2014</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + <li><b><a href="https://lists.ninenines.eu/listinfo/extend">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/archives/extend/2014-February/index.html b/archives/extend/2014-February/index.html new file mode 100644 index 00000000..493c7783 --- /dev/null +++ b/archives/extend/2014-February/index.html @@ -0,0 +1,161 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <title>The Extend February 2014 Archive by thread</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>February 2014 Archives by thread</h1> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://lists.ninenines.eu/listinfo/extend">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Mon Feb 3 19:13:04 CET 2014</i><br> + <b>Ending:</b> <i>Mon Feb 10 20:55:24 CET 2014</i><br> + <b>Messages:</b> 16<p> + <ul> + +<!--0 01391451184.324- --> +<LI><A HREF="000324.html">[99s-extend] Accept header in POST request +</A><A NAME="324"> </A> +<I>Łukasz Biedrycki +</I> + +<UL> +<!--1 01391451184.324-01391451812.325- --> +<LI><A HREF="000325.html">[99s-extend] Accept header in POST request +</A><A NAME="325"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01391451184.324-01391451812.325-01391451977.326- --> +<LI><A HREF="000326.html">[99s-extend] Accept header in POST request +</A><A NAME="326"> </A> +<I>Łukasz Biedrycki +</I> + +<UL> +<!--3 01391451184.324-01391451812.325-01391451977.326-01391452675.327- --> +<LI><A HREF="000327.html">[99s-extend] Accept header in POST request +</A><A NAME="327"> </A> +<I>Loïc Hoguin +</I> + +<!--3 01391451184.324-01391451812.325-01391451977.326-01391452675.327-01391454492.328- --> +<LI><A HREF="000328.html">[99s-extend] Accept header in POST request +</A><A NAME="328"> </A> +<I>Łukasz Biedrycki +</I> + +<!--3 01391451184.324-01391451812.325-01391451977.326-01391452675.327-01391454492.328-01391454944.329- --> +<LI><A HREF="000329.html">[99s-extend] Accept header in POST request +</A><A NAME="329"> </A> +<I>Loïc Hoguin +</I> + +<!--3 01391451184.324-01391451812.325-01391451977.326-01391452675.327-01391454492.328-01391454944.329-01391454989.330- --> +<LI><A HREF="000330.html">[99s-extend] Accept header in POST request +</A><A NAME="330"> </A> +<I>Łukasz Biedrycki +</I> + +</UL> +</UL> +</UL> +<!--0 01391792186.331- --> +<LI><A HREF="000331.html">[99s-extend] Metrics per request and handler +</A><A NAME="331"> </A> +<I>Łukasz Biedrycki +</I> + +<UL> +<!--1 01391792186.331-01392025273.332- --> +<LI><A HREF="000332.html">[99s-extend] Metrics per request and handler +</A><A NAME="332"> </A> +<I>Łukasz Biedrycki +</I> + +<UL> +<!--2 01391792186.331-01392025273.332-01392025764.333- --> +<LI><A HREF="000333.html">[99s-extend] Metrics per request and handler +</A><A NAME="333"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--3 01391792186.331-01392025273.332-01392025764.333-01392025910.334- --> +<LI><A HREF="000334.html">[99s-extend] Metrics per request and handler +</A><A NAME="334"> </A> +<I>Łukasz Biedrycki +</I> + +</UL> +</UL> +</UL> +<!--0 01392057894.335- --> +<LI><A HREF="000335.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="335"> </A> +<I>Anton Koval' +</I> + +<UL> +<!--1 01392057894.335-01392058081.336- --> +<LI><A HREF="000336.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="336"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01392057894.335-01392058081.336-01392060169.337- --> +<LI><A HREF="000337.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="337"> </A> +<I>Anton Koval' +</I> + +<UL> +<!--3 01392057894.335-01392058081.336-01392060169.337-01392061614.338- --> +<LI><A HREF="000338.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="338"> </A> +<I>Ivan Uemlianin +</I> + +<!--3 01392057894.335-01392058081.336-01392060169.337-01392061614.338-01392062124.339- --> +<LI><A HREF="000339.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="339"> </A> +<I>Anton Koval' +</I> + +</UL> +</UL> +</UL> + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Mon Feb 10 20:55:24 CET 2014</i><br> + <b>Archived on:</b> <i>Wed May 28 18:41:47 CEST 2014</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://lists.ninenines.eu/listinfo/extend">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/archives/extend/2014-February/subject.html b/archives/extend/2014-February/subject.html new file mode 100644 index 00000000..3247635a --- /dev/null +++ b/archives/extend/2014-February/subject.html @@ -0,0 +1,127 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <title>The Extend February 2014 Archive by subject</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>February 2014 Archives by subject</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://lists.ninenines.eu/listinfo/extend">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Mon Feb 3 19:13:04 CET 2014</i><br> + <b>Ending:</b> <i>Mon Feb 10 20:55:24 CET 2014</i><br> + <b>Messages:</b> 16<p> + <ul> + +<LI><A HREF="000324.html">[99s-extend] Accept header in POST request +</A><A NAME="324"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000325.html">[99s-extend] Accept header in POST request +</A><A NAME="325"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000326.html">[99s-extend] Accept header in POST request +</A><A NAME="326"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000327.html">[99s-extend] Accept header in POST request +</A><A NAME="327"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000328.html">[99s-extend] Accept header in POST request +</A><A NAME="328"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000329.html">[99s-extend] Accept header in POST request +</A><A NAME="329"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000330.html">[99s-extend] Accept header in POST request +</A><A NAME="330"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000335.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="335"> </A> +<I>Anton Koval' +</I> + +<LI><A HREF="000336.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="336"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000337.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="337"> </A> +<I>Anton Koval' +</I> + +<LI><A HREF="000338.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="338"> </A> +<I>Ivan Uemlianin +</I> + +<LI><A HREF="000339.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="339"> </A> +<I>Anton Koval' +</I> + +<LI><A HREF="000331.html">[99s-extend] Metrics per request and handler +</A><A NAME="331"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000332.html">[99s-extend] Metrics per request and handler +</A><A NAME="332"> </A> +<I>Łukasz Biedrycki +</I> + +<LI><A HREF="000333.html">[99s-extend] Metrics per request and handler +</A><A NAME="333"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000334.html">[99s-extend] Metrics per request and handler +</A><A NAME="334"> </A> +<I>Łukasz Biedrycki +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Mon Feb 10 20:55:24 CET 2014</i><br> + <b>Archived on:</b> <i>Wed May 28 18:41:47 CEST 2014</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://lists.ninenines.eu/listinfo/extend">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/archives/extend/2014-February/thread.html b/archives/extend/2014-February/thread.html new file mode 100644 index 00000000..493c7783 --- /dev/null +++ b/archives/extend/2014-February/thread.html @@ -0,0 +1,161 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <title>The Extend February 2014 Archive by thread</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>February 2014 Archives by thread</h1> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://lists.ninenines.eu/listinfo/extend">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Mon Feb 3 19:13:04 CET 2014</i><br> + <b>Ending:</b> <i>Mon Feb 10 20:55:24 CET 2014</i><br> + <b>Messages:</b> 16<p> + <ul> + +<!--0 01391451184.324- --> +<LI><A HREF="000324.html">[99s-extend] Accept header in POST request +</A><A NAME="324"> </A> +<I>Łukasz Biedrycki +</I> + +<UL> +<!--1 01391451184.324-01391451812.325- --> +<LI><A HREF="000325.html">[99s-extend] Accept header in POST request +</A><A NAME="325"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01391451184.324-01391451812.325-01391451977.326- --> +<LI><A HREF="000326.html">[99s-extend] Accept header in POST request +</A><A NAME="326"> </A> +<I>Łukasz Biedrycki +</I> + +<UL> +<!--3 01391451184.324-01391451812.325-01391451977.326-01391452675.327- --> +<LI><A HREF="000327.html">[99s-extend] Accept header in POST request +</A><A NAME="327"> </A> +<I>Loïc Hoguin +</I> + +<!--3 01391451184.324-01391451812.325-01391451977.326-01391452675.327-01391454492.328- --> +<LI><A HREF="000328.html">[99s-extend] Accept header in POST request +</A><A NAME="328"> </A> +<I>Łukasz Biedrycki +</I> + +<!--3 01391451184.324-01391451812.325-01391451977.326-01391452675.327-01391454492.328-01391454944.329- --> +<LI><A HREF="000329.html">[99s-extend] Accept header in POST request +</A><A NAME="329"> </A> +<I>Loïc Hoguin +</I> + +<!--3 01391451184.324-01391451812.325-01391451977.326-01391452675.327-01391454492.328-01391454944.329-01391454989.330- --> +<LI><A HREF="000330.html">[99s-extend] Accept header in POST request +</A><A NAME="330"> </A> +<I>Łukasz Biedrycki +</I> + +</UL> +</UL> +</UL> +<!--0 01391792186.331- --> +<LI><A HREF="000331.html">[99s-extend] Metrics per request and handler +</A><A NAME="331"> </A> +<I>Łukasz Biedrycki +</I> + +<UL> +<!--1 01391792186.331-01392025273.332- --> +<LI><A HREF="000332.html">[99s-extend] Metrics per request and handler +</A><A NAME="332"> </A> +<I>Łukasz Biedrycki +</I> + +<UL> +<!--2 01391792186.331-01392025273.332-01392025764.333- --> +<LI><A HREF="000333.html">[99s-extend] Metrics per request and handler +</A><A NAME="333"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--3 01391792186.331-01392025273.332-01392025764.333-01392025910.334- --> +<LI><A HREF="000334.html">[99s-extend] Metrics per request and handler +</A><A NAME="334"> </A> +<I>Łukasz Biedrycki +</I> + +</UL> +</UL> +</UL> +<!--0 01392057894.335- --> +<LI><A HREF="000335.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="335"> </A> +<I>Anton Koval' +</I> + +<UL> +<!--1 01392057894.335-01392058081.336- --> +<LI><A HREF="000336.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="336"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01392057894.335-01392058081.336-01392060169.337- --> +<LI><A HREF="000337.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="337"> </A> +<I>Anton Koval' +</I> + +<UL> +<!--3 01392057894.335-01392058081.336-01392060169.337-01392061614.338- --> +<LI><A HREF="000338.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="338"> </A> +<I>Ivan Uemlianin +</I> + +<!--3 01392057894.335-01392058081.336-01392060169.337-01392061614.338-01392062124.339- --> +<LI><A HREF="000339.html">[99s-extend] do not treat warnings as errors on make? +</A><A NAME="339"> </A> +<I>Anton Koval' +</I> + +</UL> +</UL> +</UL> + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Mon Feb 10 20:55:24 CET 2014</i><br> + <b>Archived on:</b> <i>Wed May 28 18:41:47 CEST 2014</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://lists.ninenines.eu/listinfo/extend">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + |