diff options
Diffstat (limited to '_build/static/archives/extend/2013-April')
60 files changed, 8138 insertions, 0 deletions
diff --git a/_build/static/archives/extend/2013-April/000073.html b/_build/static/archives/extend/2013-April/000073.html new file mode 100644 index 00000000..ce854d84 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000073.html @@ -0,0 +1,82 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] [ANN] Ranch 0.8.0 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20%5BANN%5D%20Ranch%200.8.0&In-Reply-To=%3C515B1410.6080905%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="Next" HREF="000074.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] [ANN] Ranch 0.8.0</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20%5BANN%5D%20Ranch%200.8.0&In-Reply-To=%3C515B1410.6080905%40ninenines.eu%3E" + TITLE="[99s-extend] [ANN] Ranch 0.8.0">essen at ninenines.eu + </A><BR> + <I>Tue Apr 2 19:23:28 CEST 2013</I> + <P><UL> + + <LI>Next message: <A HREF="000074.html">[99s-extend] [ANN] Cowboy 0.8.3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#73">[ date ]</a> + <a href="thread.html#73">[ thread ]</a> + <a href="subject.html#73">[ subject ]</a> + <a href="author.html#73">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Just released! + +We have greatly improved the performance of Ranch both for accepting +connections and when they get disconnected. Stability has also been much +improved thanks to many community provided tests. + +Small API changes. Sorry! + + * ListenerPid argument to Protocol:start_link/4 became Ref + * as a result it's now ranch:accept_ack(Ref) + * ranch_listener:remove_connection(ListenerPid) became +ranch:remove_connection(Ref) + +Unless you used ranch_listener_remove_connection/1 your old code should +still work without any changes. + +Enjoy! + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="000074.html">[99s-extend] [ANN] Cowboy 0.8.3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#73">[ date ]</a> + <a href="thread.html#73">[ thread ]</a> + <a href="subject.html#73">[ subject ]</a> + <a href="author.html#73">[ 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/_build/static/archives/extend/2013-April/000074.html b/_build/static/archives/extend/2013-April/000074.html new file mode 100644 index 00000000..4618e32d --- /dev/null +++ b/_build/static/archives/extend/2013-April/000074.html @@ -0,0 +1,78 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] [ANN] Cowboy 0.8.3 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20%5BANN%5D%20Cowboy%200.8.3&In-Reply-To=%3C515C48EC.7040403%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="000073.html"> + <LINK REL="Next" HREF="000075.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] [ANN] Cowboy 0.8.3</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20%5BANN%5D%20Cowboy%200.8.3&In-Reply-To=%3C515C48EC.7040403%40ninenines.eu%3E" + TITLE="[99s-extend] [ANN] Cowboy 0.8.3">essen at ninenines.eu + </A><BR> + <I>Wed Apr 3 17:21:16 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000073.html">[99s-extend] [ANN] Ranch 0.8.0 +</A></li> + <LI>Next message: <A HREF="000075.html">[99s-extend] Response headers +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#74">[ date ]</a> + <a href="thread.html#74">[ thread ]</a> + <a href="subject.html#74">[ subject ]</a> + <a href="author.html#74">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello! + +Very small release just to update Ranch to 0.8.0 (faster!) and change +something about streaming the body. Newly introduced init_stream/5 +proved to be a bad idea and got removed in favor of a new stream_body/2 +which allows specifying the maximum chunk size you want on a per chunk +basis. + + <A HREF="https://github.com/extend/cowboy">https://github.com/extend/cowboy</A> + +Enjoy! + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000073.html">[99s-extend] [ANN] Ranch 0.8.0 +</A></li> + <LI>Next message: <A HREF="000075.html">[99s-extend] Response headers +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#74">[ date ]</a> + <a href="thread.html#74">[ thread ]</a> + <a href="subject.html#74">[ subject ]</a> + <a href="author.html#74">[ 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/_build/static/archives/extend/2013-April/000075.html b/_build/static/archives/extend/2013-April/000075.html new file mode 100644 index 00000000..3441177d --- /dev/null +++ b/_build/static/archives/extend/2013-April/000075.html @@ -0,0 +1,66 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Response headers + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Response%20headers&In-Reply-To=%3CCE8DCDF4-398A-42CA-BCBE-8342F5D00DEF%40gmail.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="000074.html"> + <LINK REL="Next" HREF="000076.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Response headers</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Response%20headers&In-Reply-To=%3CCE8DCDF4-398A-42CA-BCBE-8342F5D00DEF%40gmail.com%3E" + TITLE="[99s-extend] Response headers">lee.sylvester at gmail.com + </A><BR> + <I>Wed Apr 3 21:33:20 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000074.html">[99s-extend] [ANN] Cowboy 0.8.3 +</A></li> + <LI>Next message: <A HREF="000076.html">[99s-extend] Response headers +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#75">[ date ]</a> + <a href="thread.html#75">[ thread ]</a> + <a href="subject.html#75">[ subject ]</a> + <a href="author.html#75">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi list, + +I'd like to set up my handler to use CORS. Can anyone tell me how I can modify the headers for my handler to support this? + +Thanks loads, +Lee +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000074.html">[99s-extend] [ANN] Cowboy 0.8.3 +</A></li> + <LI>Next message: <A HREF="000076.html">[99s-extend] Response headers +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#75">[ date ]</a> + <a href="thread.html#75">[ thread ]</a> + <a href="subject.html#75">[ subject ]</a> + <a href="author.html#75">[ 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/_build/static/archives/extend/2013-April/000076.html b/_build/static/archives/extend/2013-April/000076.html new file mode 100644 index 00000000..243e1929 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000076.html @@ -0,0 +1,196 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Response headers + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Response%20headers&In-Reply-To=%3CCD81FF59.4478%25christopher.phillips%40turner.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="000075.html"> + <LINK REL="Next" HREF="000077.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Response headers</H1> + <B>Phillips, Christopher</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Response%20headers&In-Reply-To=%3CCD81FF59.4478%25christopher.phillips%40turner.com%3E" + TITLE="[99s-extend] Response headers">Christopher.Phillips at turner.com + </A><BR> + <I>Wed Apr 3 22:35:36 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000075.html">[99s-extend] Response headers +</A></li> + <LI>Next message: <A HREF="000077.html">[99s-extend] Response headers +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#76">[ date ]</a> + <a href="thread.html#76">[ thread ]</a> + <a href="subject.html#76">[ subject ]</a> + <a href="author.html#76">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> + Sure. Right now, Cowboy doesn't parse the headers, but you can manually +parse them in your handler. I've got them working in my implementation +pretty well, I'll try and break it down a bit here. + + A good, basic overview of what the requests the browser will send, and +what your responses should look like, is here: +<A HREF="https://developer.mozilla.org/en-US/docs/HTTP/Access_control_CORS">https://developer.mozilla.org/en-US/docs/HTTP/Access_control_CORS</A> + + + +HANDLING PRE-FLIGHTS - + Pre-flights are the OPTION requests the browser automatically sends off +when you make a CORS request using a verb other than GET, or POST with one +of three acceptable content types. They're defined well in the above link. + + You can read off the requested headers the actual call wants to send in +the OPTIONS preflight with + + {Headers, NewRequest } = +cowboy_req:header(<<"access-control-request-headers">>, Request) + + Headers will either be the binary, or undefined. If the binary, you +either need to manually parse it and choose to allow/disallow the request +from continuing based on it, or, if you just want to allow all headers +trivially, just pipe that back into the request, a la - + + Request2 = +cowboy_req:set_resp_header(<<"access-control-allow-headers">>, +binary_to_list(Headers), NewRequest) + + (As a reminder, it can be undefined. You'll need to check for that +before passing it into the above. If it's undefined, you don't need to add +the access-control-allow-headers header). + + + + As part of the pre-flight request, you also need to handle what methods +are allowed. This looks something like - + + PreflightedRequest = +cowboy_req:set_resp_header(<<"access-control-allow-methods">>, <<"GET, +POST, DELETE, PUT">>, Request2) + + If I wanted to allow gets, posts, deletes, and puts. You can also choose +to read off the access-control-request-method header sent from the client, +but I don't see the point; your list of allowed methods doesn't need to +change based on that (the user is requesting a POST, why does that change +whether you allow a POST or not? But I digress). + + + + + +FOR ALL CALLS (both pre-flights and the actual call) + Respond with acceptable origin. If you want any domain to access this +resource (not advised, unless this is a public, readonly resource, but +good for testing), you can do - + + NewRequest = +cowboy_req:set_resp_header(<<"access-control-allow-origin">>, <<"*">>, +Request) + + + If you want to filter out the allowed domains, it looks like - + + Origin = cowboy_req:header(<<"origin">>, Request) %Get the origin that +the browser sent you + + %Do logic to check Origin, and any other data that would decide +whether this request is allowed; it will only apply on a CORS request from +another browser. + + %If it passes, pass Origin back as the value for the +access-control-allow-origin header. + NewRequest = +cowboy_req:set_resp_header(<<"access-control-allow-origin">>, Origin, +Request) + + + +FOR ONLY THE ACTUAL CALL + If you want to send custom headers back to your Javascript client (or +read any standard header beyond content-type), you need to explicitly +allow them. This looks like (if I wanted to expose the 'server' header so +my client Javascript can see that it's Cowboy on the backend) - + + ExposedHeaderRequest = +cowboy_req:set_resp_header(<<"access-control-expose-headers">>, +<<"server">>, Request) + + + + + That's basically it I believe. There is also a max age, and a allow +credentials header (which is really more of a require credentials); +they're pretty straightforwardly explained on that page I linked above, +but I haven't played with them personally. + + + Caveats I ran into were largely being aware that same domain requests do +NOT supply any of the CORS headers, not even the origin header (so you can +get undefined and have to handle those cases), as well as understanding +the ramifications of allowing cross domain requests. Also, if you want to +develop while disconnected (or if it's not easy to grab another domain), +use your hosts file to declare a fake domain pointed to 127.0.0.1, load +your page from that, explicitly define your AJAX calls to localhost. Note +too that there is a bug in Firefox at present when you try and get all the +request headers. It returns an empty list. You can get individual ones if +you know the name (I.e., getResponseHeader("server") will work, +getAllResponseHeaders() returns an empty string). This is further +compounded by jQuery building its own XHR that loads headers by calling +getAllResponseHeaders, so in Firefox, using jQuery, you can get back zero +headers. Don't know if that affects you, but it's an issue it took me a +good while to diagnose, and which we've had to bear in mind. + + + + +On 4/3/13 3:33 PM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: + +><i>Hi list, +</I>><i> +</I>><i>I'd like to set up my handler to use CORS. Can anyone tell me how I can +</I>><i>modify the headers for my handler to support this? +</I>><i> +</I>><i>Thanks loads, +</I>><i>Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I> + + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000075.html">[99s-extend] Response headers +</A></li> + <LI>Next message: <A HREF="000077.html">[99s-extend] Response headers +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#76">[ date ]</a> + <a href="thread.html#76">[ thread ]</a> + <a href="subject.html#76">[ subject ]</a> + <a href="author.html#76">[ 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/_build/static/archives/extend/2013-April/000077.html b/_build/static/archives/extend/2013-April/000077.html new file mode 100644 index 00000000..1bbf7ad2 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000077.html @@ -0,0 +1,213 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Response headers + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Response%20headers&In-Reply-To=%3C3E75C3ED-9F52-495A-8E04-EF0A4667DB4E%40gmail.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="000076.html"> + <LINK REL="Next" HREF="000078.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Response headers</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Response%20headers&In-Reply-To=%3C3E75C3ED-9F52-495A-8E04-EF0A4667DB4E%40gmail.com%3E" + TITLE="[99s-extend] Response headers">lee.sylvester at gmail.com + </A><BR> + <I>Thu Apr 4 10:38:07 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000076.html">[99s-extend] Response headers +</A></li> + <LI>Next message: <A HREF="000078.html">[99s-extend] Bullet connection +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#77">[ date ]</a> + <a href="thread.html#77">[ thread ]</a> + <a href="subject.html#77">[ subject ]</a> + <a href="author.html#77">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi Christopher, + +Thank you for that. I will attempt to go through each piece today and solve the problem. This is good advice; maybe it belongs in a blog post? :-) + +Thanks again, +Lee + + + + +On 3 Apr 2013, at 21:35, "Phillips, Christopher" <<A HREF="https://lists.ninenines.eu/listinfo/extend">Christopher.Phillips at turner.com</A>> wrote: + +><i> +</I>><i> Sure. Right now, Cowboy doesn't parse the headers, but you can manually +</I>><i> parse them in your handler. I've got them working in my implementation +</I>><i> pretty well, I'll try and break it down a bit here. +</I>><i> +</I>><i> A good, basic overview of what the requests the browser will send, and +</I>><i> what your responses should look like, is here: +</I>><i> <A HREF="https://developer.mozilla.org/en-US/docs/HTTP/Access_control_CORS">https://developer.mozilla.org/en-US/docs/HTTP/Access_control_CORS</A> +</I>><i> +</I>><i> +</I>><i> +</I>><i> HANDLING PRE-FLIGHTS - +</I>><i> Pre-flights are the OPTION requests the browser automatically sends off +</I>><i> when you make a CORS request using a verb other than GET, or POST with one +</I>><i> of three acceptable content types. They're defined well in the above link. +</I>><i> +</I>><i> You can read off the requested headers the actual call wants to send in +</I>><i> the OPTIONS preflight with +</I>><i> +</I>><i> {Headers, NewRequest } = +</I>><i> cowboy_req:header(<<"access-control-request-headers">>, Request) +</I>><i> +</I>><i> Headers will either be the binary, or undefined. If the binary, you +</I>><i> either need to manually parse it and choose to allow/disallow the request +</I>><i> from continuing based on it, or, if you just want to allow all headers +</I>><i> trivially, just pipe that back into the request, a la - +</I>><i> +</I>><i> Request2 = +</I>><i> cowboy_req:set_resp_header(<<"access-control-allow-headers">>, +</I>><i> binary_to_list(Headers), NewRequest) +</I>><i> +</I>><i> (As a reminder, it can be undefined. You'll need to check for that +</I>><i> before passing it into the above. If it's undefined, you don't need to add +</I>><i> the access-control-allow-headers header). +</I>><i> +</I>><i> +</I>><i> +</I>><i> As part of the pre-flight request, you also need to handle what methods +</I>><i> are allowed. This looks something like - +</I>><i> +</I>><i> PreflightedRequest = +</I>><i> cowboy_req:set_resp_header(<<"access-control-allow-methods">>, <<"GET, +</I>><i> POST, DELETE, PUT">>, Request2) +</I>><i> +</I>><i> If I wanted to allow gets, posts, deletes, and puts. You can also choose +</I>><i> to read off the access-control-request-method header sent from the client, +</I>><i> but I don't see the point; your list of allowed methods doesn't need to +</I>><i> change based on that (the user is requesting a POST, why does that change +</I>><i> whether you allow a POST or not? But I digress). +</I>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i> FOR ALL CALLS (both pre-flights and the actual call) +</I>><i> Respond with acceptable origin. If you want any domain to access this +</I>><i> resource (not advised, unless this is a public, readonly resource, but +</I>><i> good for testing), you can do - +</I>><i> +</I>><i> NewRequest = +</I>><i> cowboy_req:set_resp_header(<<"access-control-allow-origin">>, <<"*">>, +</I>><i> Request) +</I>><i> +</I>><i> +</I>><i> If you want to filter out the allowed domains, it looks like - +</I>><i> +</I>><i> Origin = cowboy_req:header(<<"origin">>, Request) %Get the origin that +</I>><i> the browser sent you +</I>><i> +</I>><i> %Do logic to check Origin, and any other data that would decide +</I>><i> whether this request is allowed; it will only apply on a CORS request from +</I>><i> another browser. +</I>><i> +</I>><i> %If it passes, pass Origin back as the value for the +</I>><i> access-control-allow-origin header. +</I>><i> NewRequest = +</I>><i> cowboy_req:set_resp_header(<<"access-control-allow-origin">>, Origin, +</I>><i> Request) +</I>><i> +</I>><i> +</I>><i> +</I>><i> FOR ONLY THE ACTUAL CALL +</I>><i> If you want to send custom headers back to your Javascript client (or +</I>><i> read any standard header beyond content-type), you need to explicitly +</I>><i> allow them. This looks like (if I wanted to expose the 'server' header so +</I>><i> my client Javascript can see that it's Cowboy on the backend) - +</I>><i> +</I>><i> ExposedHeaderRequest = +</I>><i> cowboy_req:set_resp_header(<<"access-control-expose-headers">>, +</I>><i> <<"server">>, Request) +</I>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i> That's basically it I believe. There is also a max age, and a allow +</I>><i> credentials header (which is really more of a require credentials); +</I>><i> they're pretty straightforwardly explained on that page I linked above, +</I>><i> but I haven't played with them personally. +</I>><i> +</I>><i> +</I>><i> Caveats I ran into were largely being aware that same domain requests do +</I>><i> NOT supply any of the CORS headers, not even the origin header (so you can +</I>><i> get undefined and have to handle those cases), as well as understanding +</I>><i> the ramifications of allowing cross domain requests. Also, if you want to +</I>><i> develop while disconnected (or if it's not easy to grab another domain), +</I>><i> use your hosts file to declare a fake domain pointed to 127.0.0.1, load +</I>><i> your page from that, explicitly define your AJAX calls to localhost. Note +</I>><i> too that there is a bug in Firefox at present when you try and get all the +</I>><i> request headers. It returns an empty list. You can get individual ones if +</I>><i> you know the name (I.e., getResponseHeader("server") will work, +</I>><i> getAllResponseHeaders() returns an empty string). This is further +</I>><i> compounded by jQuery building its own XHR that loads headers by calling +</I>><i> getAllResponseHeaders, so in Firefox, using jQuery, you can get back zero +</I>><i> headers. Don't know if that affects you, but it's an issue it took me a +</I>><i> good while to diagnose, and which we've had to bear in mind. +</I>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i> On 4/3/13 3:33 PM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>><i> +</I>>><i> Hi list, +</I>>><i> +</I>>><i> I'd like to set up my handler to use CORS. Can anyone tell me how I can +</I>>><i> modify the headers for my handler to support this? +</I>>><i> +</I>>><i> Thanks loads, +</I>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000076.html">[99s-extend] Response headers +</A></li> + <LI>Next message: <A HREF="000078.html">[99s-extend] Bullet connection +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#77">[ date ]</a> + <a href="thread.html#77">[ thread ]</a> + <a href="subject.html#77">[ subject ]</a> + <a href="author.html#77">[ 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/_build/static/archives/extend/2013-April/000078.html b/_build/static/archives/extend/2013-April/000078.html new file mode 100644 index 00000000..03f7f5d0 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000078.html @@ -0,0 +1,68 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Bullet connection + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Bullet%20connection&In-Reply-To=%3C33516651-FC93-49EA-A8CA-B5C3E42B03E5%40gmail.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="000077.html"> + <LINK REL="Next" HREF="000079.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Bullet connection</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Bullet%20connection&In-Reply-To=%3C33516651-FC93-49EA-A8CA-B5C3E42B03E5%40gmail.com%3E" + TITLE="[99s-extend] Bullet connection">lee.sylvester at gmail.com + </A><BR> + <I>Thu Apr 4 22:17:54 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000077.html">[99s-extend] Response headers +</A></li> + <LI>Next message: <A HREF="000079.html">[99s-extend] Bullet connection +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#78">[ date ]</a> + <a href="thread.html#78">[ thread ]</a> + <a href="subject.html#78">[ subject ]</a> + <a href="author.html#78">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi guys, + +So, I'm using bullet in my Cowboy setup. There's a lot of tasks that take place before a connection is finally requested, but when it is requested, I see that the server is first called via HTTPS using method CONNECT. The problem I have is that, while testing this on local host, this CONNECT request is throwing a 500 error, stating "SSL Proxying not enabled for this host: enable in Proxy Settings, SSL locations". + +Does anyone know how I fix this to get past this problem? + +Thanks, +Lee +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000077.html">[99s-extend] Response headers +</A></li> + <LI>Next message: <A HREF="000079.html">[99s-extend] Bullet connection +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#78">[ date ]</a> + <a href="thread.html#78">[ thread ]</a> + <a href="subject.html#78">[ subject ]</a> + <a href="author.html#78">[ 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/_build/static/archives/extend/2013-April/000079.html b/_build/static/archives/extend/2013-April/000079.html new file mode 100644 index 00000000..c44417d0 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000079.html @@ -0,0 +1,76 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Bullet connection + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Bullet%20connection&In-Reply-To=%3C515DE504.5060007%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="000078.html"> + <LINK REL="Next" HREF="000080.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Bullet connection</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Bullet%20connection&In-Reply-To=%3C515DE504.5060007%40ninenines.eu%3E" + TITLE="[99s-extend] Bullet connection">essen at ninenines.eu + </A><BR> + <I>Thu Apr 4 22:39:32 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000078.html">[99s-extend] Bullet connection +</A></li> + <LI>Next message: <A HREF="000080.html">[99s-extend] Bullet connection +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#79">[ date ]</a> + <a href="thread.html#79">[ thread ]</a> + <a href="subject.html#79">[ subject ]</a> + <a href="author.html#79">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 04/04/2013 10:17 PM, Lee Sylvester wrote: +><i> Hi guys, +</I>><i> +</I>><i> So, I'm using bullet in my Cowboy setup. There's a lot of tasks that take place before a connection is finally requested, but when it is requested, I see that the server is first called via HTTPS using method CONNECT. The problem I have is that, while testing this on local host, this CONNECT request is throwing a 500 error, stating "SSL Proxying not enabled for this host: enable in Proxy Settings, SSL locations". +</I>><i> +</I>><i> Does anyone know how I fix this to get past this problem? +</I> +You should probably disable the proxy you have configured in your +browser for the domain localhost. + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000078.html">[99s-extend] Bullet connection +</A></li> + <LI>Next message: <A HREF="000080.html">[99s-extend] Bullet connection +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#79">[ date ]</a> + <a href="thread.html#79">[ thread ]</a> + <a href="subject.html#79">[ subject ]</a> + <a href="author.html#79">[ 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/_build/static/archives/extend/2013-April/000080.html b/_build/static/archives/extend/2013-April/000080.html new file mode 100644 index 00000000..ed41aaf8 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000080.html @@ -0,0 +1,87 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Bullet connection + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Bullet%20connection&In-Reply-To=%3C52A2CDB5-3C4D-4E20-ACDF-011A44E0FD8B%40gmail.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="000079.html"> + <LINK REL="Next" HREF="000081.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Bullet connection</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Bullet%20connection&In-Reply-To=%3C52A2CDB5-3C4D-4E20-ACDF-011A44E0FD8B%40gmail.com%3E" + TITLE="[99s-extend] Bullet connection">lee.sylvester at gmail.com + </A><BR> + <I>Thu Apr 4 22:54:54 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000079.html">[99s-extend] Bullet connection +</A></li> + <LI>Next message: <A HREF="000081.html">[99s-extend] Problems with Bullet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#80">[ date ]</a> + <a href="thread.html#80">[ thread ]</a> + <a href="subject.html#80">[ subject ]</a> + <a href="author.html#80">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>D'oh! I'm obviously tired :( Thanks for that. I saw the message and instantly assumed it was a Cowboy related error. Okay, so I got that fixed. Now I need to work out why my connections close the instant they're open :-D Oh, the life of a developer! + +Thanks again. + +Lee + + + + +On 4 Apr 2013, at 21:39, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: + +><i> On 04/04/2013 10:17 PM, Lee Sylvester wrote: +</I>>><i> Hi guys, +</I>>><i> +</I>>><i> So, I'm using bullet in my Cowboy setup. There's a lot of tasks that take place before a connection is finally requested, but when it is requested, I see that the server is first called via HTTPS using method CONNECT. The problem I have is that, while testing this on local host, this CONNECT request is throwing a 500 error, stating "SSL Proxying not enabled for this host: enable in Proxy Settings, SSL locations". +</I>>><i> +</I>>><i> Does anyone know how I fix this to get past this problem? +</I>><i> +</I>><i> You should probably disable the proxy you have configured in your browser for the domain localhost. +</I>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> Erlang Cowboy +</I>><i> Nine Nines +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000079.html">[99s-extend] Bullet connection +</A></li> + <LI>Next message: <A HREF="000081.html">[99s-extend] Problems with Bullet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#80">[ date ]</a> + <a href="thread.html#80">[ thread ]</a> + <a href="subject.html#80">[ subject ]</a> + <a href="author.html#80">[ 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/_build/static/archives/extend/2013-April/000081.html b/_build/static/archives/extend/2013-April/000081.html new file mode 100644 index 00000000..a19b56a9 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000081.html @@ -0,0 +1,156 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Problems with Bullet + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Problems%20with%20Bullet&In-Reply-To=%3CB09B2F4B-4842-430D-A3AB-AC132B646E04%40gmail.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="000080.html"> + <LINK REL="Next" HREF="000082.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Problems with Bullet</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Problems%20with%20Bullet&In-Reply-To=%3CB09B2F4B-4842-430D-A3AB-AC132B646E04%40gmail.com%3E" + TITLE="[99s-extend] Problems with Bullet">lee.sylvester at gmail.com + </A><BR> + <I>Mon Apr 8 15:53:38 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000080.html">[99s-extend] Bullet connection +</A></li> + <LI>Next message: <A HREF="000082.html">[99s-extend] Problems with Bullet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#81">[ date ]</a> + <a href="thread.html#81">[ thread ]</a> + <a href="subject.html#81">[ subject ]</a> + <a href="author.html#81">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi all, + +I'm currently having problems getting a websocket to connect to a simple bare bones Bullet handler. Unfortunately, I'm still quite an Erlang noob, so the stack traces tend to lead me in circles. I'm hoping this is obvious stuff to you Erlang pros :-) + +Given the below handler: + +init(_Transport, Req, _Opts, _Active) -> + {ok, Req, undefined_state}. + +stream(Data, Req, State) -> + {ok, Req, State}. + +info(Info, Req, State) -> + {reply, Info, Req, State}. + +terminate(_Req, _State) -> + ok. + +Connecting with a websocket throws the following error: + +=ERROR REPORT==== 8-Apr-2013::14:46:11 === +** Cowboy handler bullet_handler terminating in init/3 + for the reason error:undef +** Options were [{handler,connection_handler}] +** Request was [{socket,#Port<0.926>}, + {transport,ranch_tcp}, + {connection,keepalive}, + {pid,<0.491.0>}, + {method,<<"GET">>}, + {version,{1,1}}, + {peer,{{127,0,0,1},56630}}, + {host,<<"localhost">>}, + {host_info,undefined}, + {port,8080}, + {path,<<"/">>}, + {path_info,undefined}, + {qs,<<"encoding=text">>}, + {qs_vals,undefined}, + {fragment,<<>>}, + {bindings,[]}, + {headers,[{<<"upgrade">>,<<"websocket">>}, + {<<"connection">>,<<"Upgrade">>}, + {<<"host">>,<<"localhost:8080">>}, + {<<"origin">>,<<"<A HREF="http://www.websocket.org">http://www.websocket.org</A>">>}, + {<<"pragma">>,<<"no-cache">>}, + {<<"cache-control">>,<<"no-cache">>}, + {<<"sec-websocket-key">>, + <<"fEj/SOOcQgSKATOjhbNJBQ==">>}, + {<<"sec-websocket-version">>,<<"13">>}, + {<<"sec-websocket-extensions">>, + <<"x-webkit-deflate-frame">>}]}, + {p_headers,[{<<"connection">>,[<<"upgrade">>]}]}, + {cookies,undefined}, + {meta,[]}, + {body_state,waiting}, + {multipart,undefined}, + {buffer,<<>>}, + {resp_compress,false}, + {resp_state,waiting}, + {resp_headers,[]}, + {resp_body,<<>>}, + {onresponse,undefined}] +** Stacktrace: [{bullet_handler,init, + [{tcp,http}, + {http_req,#Port<0.926>,ranch_tcp,keepalive,<0.491.0>, + <<"GET">>, + {1,1}, + {{127,0,0,1},56630}, + <<"localhost">>,undefined,8080,<<"/">>, + undefined,<<"encoding=text">>,undefined,<<>>, + [], + [{<<"upgrade">>,<<"websocket">>}, + {<<"connection">>,<<"Upgrade">>}, + {<<"host">>,<<"localhost:8080">>}, + {<<"origin">>,<<"<A HREF="http://www.websocket.org">http://www.websocket.org</A>">>}, + {<<"pragma">>,<<"no-cache">>}, + {<<"cache-control">>,<<"no-cache">>}, + {<<"sec-websocket-key">>, + <<"fEj/SOOcQgSKATOjhbNJBQ==">>}, + {<<"sec-websocket-version">>,<<"13">>}, + {<<"sec-websocket-extensions">>, + <<"x-webkit-deflate-frame">>}], + [{<<"connection">>,[<<"upgrade">>]}], + undefined,[],waiting,undefined,<<>>,false,waiting,[], + <<>>,undefined}, + [{handler,connection_handler}]], + []}, + {cowboy_handler,handler_init,4, + [{file,"src/cowboy_handler.erl"},{line,69}]}, + {cowboy_protocol,execute,4, + [{file,"src/cowboy_protocol.erl"},{line,514}]}] + +Can anyone see what might be throwing this off? I'd like to get a minimal handler running before I attempt to add some logic. + +Thanks, +Lee +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000080.html">[99s-extend] Bullet connection +</A></li> + <LI>Next message: <A HREF="000082.html">[99s-extend] Problems with Bullet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#81">[ date ]</a> + <a href="thread.html#81">[ thread ]</a> + <a href="subject.html#81">[ subject ]</a> + <a href="author.html#81">[ 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/_build/static/archives/extend/2013-April/000082.html b/_build/static/archives/extend/2013-April/000082.html new file mode 100644 index 00000000..6c776c44 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000082.html @@ -0,0 +1,172 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Problems with Bullet + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Problems%20with%20Bullet&In-Reply-To=%3C5162CF5F.2060200%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="000081.html"> + <LINK REL="Next" HREF="000084.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Problems with Bullet</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Problems%20with%20Bullet&In-Reply-To=%3C5162CF5F.2060200%40ninenines.eu%3E" + TITLE="[99s-extend] Problems with Bullet">essen at ninenines.eu + </A><BR> + <I>Mon Apr 8 16:08:31 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000081.html">[99s-extend] Problems with Bullet +</A></li> + <LI>Next message: <A HREF="000084.html">[99s-extend] Problems with Bullet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#82">[ date ]</a> + <a href="thread.html#82">[ thread ]</a> + <a href="subject.html#82">[ subject ]</a> + <a href="author.html#82">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Sounds like Bullet isn't in your path. Forgot -pa deps/*/ebin? + +On 04/08/2013 03:53 PM, Lee Sylvester wrote: +><i> Hi all, +</I>><i> +</I>><i> I'm currently having problems getting a websocket to connect to a simple bare bones Bullet handler. Unfortunately, I'm still quite an Erlang noob, so the stack traces tend to lead me in circles. I'm hoping this is obvious stuff to you Erlang pros :-) +</I>><i> +</I>><i> Given the below handler: +</I>><i> +</I>><i> init(_Transport, Req, _Opts, _Active) -> +</I>><i> {ok, Req, undefined_state}. +</I>><i> +</I>><i> stream(Data, Req, State) -> +</I>><i> {ok, Req, State}. +</I>><i> +</I>><i> info(Info, Req, State) -> +</I>><i> {reply, Info, Req, State}. +</I>><i> +</I>><i> terminate(_Req, _State) -> +</I>><i> ok. +</I>><i> +</I>><i> Connecting with a websocket throws the following error: +</I>><i> +</I>><i> =ERROR REPORT==== 8-Apr-2013::14:46:11 === +</I>><i> ** Cowboy handler bullet_handler terminating in init/3 +</I>><i> for the reason error:undef +</I>><i> ** Options were [{handler,connection_handler}] +</I>><i> ** Request was [{socket,#Port<0.926>}, +</I>><i> {transport,ranch_tcp}, +</I>><i> {connection,keepalive}, +</I>><i> {pid,<0.491.0>}, +</I>><i> {method,<<"GET">>}, +</I>><i> {version,{1,1}}, +</I>><i> {peer,{{127,0,0,1},56630}}, +</I>><i> {host,<<"localhost">>}, +</I>><i> {host_info,undefined}, +</I>><i> {port,8080}, +</I>><i> {path,<<"/">>}, +</I>><i> {path_info,undefined}, +</I>><i> {qs,<<"encoding=text">>}, +</I>><i> {qs_vals,undefined}, +</I>><i> {fragment,<<>>}, +</I>><i> {bindings,[]}, +</I>><i> {headers,[{<<"upgrade">>,<<"websocket">>}, +</I>><i> {<<"connection">>,<<"Upgrade">>}, +</I>><i> {<<"host">>,<<"localhost:8080">>}, +</I>><i> {<<"origin">>,<<"<A HREF="http://www.websocket.org">http://www.websocket.org</A>">>}, +</I>><i> {<<"pragma">>,<<"no-cache">>}, +</I>><i> {<<"cache-control">>,<<"no-cache">>}, +</I>><i> {<<"sec-websocket-key">>, +</I>><i> <<"fEj/SOOcQgSKATOjhbNJBQ==">>}, +</I>><i> {<<"sec-websocket-version">>,<<"13">>}, +</I>><i> {<<"sec-websocket-extensions">>, +</I>><i> <<"x-webkit-deflate-frame">>}]}, +</I>><i> {p_headers,[{<<"connection">>,[<<"upgrade">>]}]}, +</I>><i> {cookies,undefined}, +</I>><i> {meta,[]}, +</I>><i> {body_state,waiting}, +</I>><i> {multipart,undefined}, +</I>><i> {buffer,<<>>}, +</I>><i> {resp_compress,false}, +</I>><i> {resp_state,waiting}, +</I>><i> {resp_headers,[]}, +</I>><i> {resp_body,<<>>}, +</I>><i> {onresponse,undefined}] +</I>><i> ** Stacktrace: [{bullet_handler,init, +</I>><i> [{tcp,http}, +</I>><i> {http_req,#Port<0.926>,ranch_tcp,keepalive,<0.491.0>, +</I>><i> <<"GET">>, +</I>><i> {1,1}, +</I>><i> {{127,0,0,1},56630}, +</I>><i> <<"localhost">>,undefined,8080,<<"/">>, +</I>><i> undefined,<<"encoding=text">>,undefined,<<>>, +</I>><i> [], +</I>><i> [{<<"upgrade">>,<<"websocket">>}, +</I>><i> {<<"connection">>,<<"Upgrade">>}, +</I>><i> {<<"host">>,<<"localhost:8080">>}, +</I>><i> {<<"origin">>,<<"<A HREF="http://www.websocket.org">http://www.websocket.org</A>">>}, +</I>><i> {<<"pragma">>,<<"no-cache">>}, +</I>><i> {<<"cache-control">>,<<"no-cache">>}, +</I>><i> {<<"sec-websocket-key">>, +</I>><i> <<"fEj/SOOcQgSKATOjhbNJBQ==">>}, +</I>><i> {<<"sec-websocket-version">>,<<"13">>}, +</I>><i> {<<"sec-websocket-extensions">>, +</I>><i> <<"x-webkit-deflate-frame">>}], +</I>><i> [{<<"connection">>,[<<"upgrade">>]}], +</I>><i> undefined,[],waiting,undefined,<<>>,false,waiting,[], +</I>><i> <<>>,undefined}, +</I>><i> [{handler,connection_handler}]], +</I>><i> []}, +</I>><i> {cowboy_handler,handler_init,4, +</I>><i> [{file,"src/cowboy_handler.erl"},{line,69}]}, +</I>><i> {cowboy_protocol,execute,4, +</I>><i> [{file,"src/cowboy_protocol.erl"},{line,514}]}] +</I>><i> +</I>><i> Can anyone see what might be throwing this off? I'd like to get a minimal handler running before I attempt to add some logic. +</I>><i> +</I>><i> Thanks, +</I>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I> + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000081.html">[99s-extend] Problems with Bullet +</A></li> + <LI>Next message: <A HREF="000084.html">[99s-extend] Problems with Bullet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#82">[ date ]</a> + <a href="thread.html#82">[ thread ]</a> + <a href="subject.html#82">[ subject ]</a> + <a href="author.html#82">[ 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/_build/static/archives/extend/2013-April/000083.html b/_build/static/archives/extend/2013-April/000083.html new file mode 100644 index 00000000..4ebd5c3f --- /dev/null +++ b/_build/static/archives/extend/2013-April/000083.html @@ -0,0 +1,179 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Problems with Bullet + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Problems%20with%20Bullet&In-Reply-To=%3CCD884493.47E3%25christopher.phillips%40turner.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="000085.html"> + <LINK REL="Next" HREF="000086.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Problems with Bullet</H1> + <B>Phillips, Christopher</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Problems%20with%20Bullet&In-Reply-To=%3CCD884493.47E3%25christopher.phillips%40turner.com%3E" + TITLE="[99s-extend] Problems with Bullet">Christopher.Phillips at turner.com + </A><BR> + <I>Mon Apr 8 16:11:44 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000085.html">[99s-extend] Problems with Bullet +</A></li> + <LI>Next message: <A HREF="000086.html">[99s-extend] Heartbeat? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#83">[ date ]</a> + <a href="thread.html#83">[ thread ]</a> + <a href="subject.html#83">[ subject ]</a> + <a href="author.html#83">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> Can you get the clock example working? I'm not sure why the initial +upgrade request would fail; are you exporting init/4 in your handler? Are +your dependencies consistent (I.e., blow them away and regrab them in case +it's an older version of cowboy with a new version of bullet, or vice +versa, maybe)? Either way, starting from the example would allow you to +start from a set of working code and either avoid the issue entirely, or +isolate it from your code. + +On 4/8/13 9:53 AM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: + +><i>Hi all, +</I>><i> +</I>><i>I'm currently having problems getting a websocket to connect to a simple +</I>><i>bare bones Bullet handler. Unfortunately, I'm still quite an Erlang +</I>><i>noob, so the stack traces tend to lead me in circles. I'm hoping this is +</I>><i>obvious stuff to you Erlang pros :-) +</I>><i> +</I>><i>Given the below handler: +</I>><i> +</I>><i>init(_Transport, Req, _Opts, _Active) -> +</I>><i> {ok, Req, undefined_state}. +</I>><i> +</I>><i>stream(Data, Req, State) -> +</I>><i> {ok, Req, State}. +</I>><i> +</I>><i>info(Info, Req, State) -> +</I>><i> {reply, Info, Req, State}. +</I>><i> +</I>><i>terminate(_Req, _State) -> +</I>><i> ok. +</I>><i> +</I>><i>Connecting with a websocket throws the following error: +</I>><i> +</I>><i>=ERROR REPORT==== 8-Apr-2013::14:46:11 === +</I>><i>** Cowboy handler bullet_handler terminating in init/3 +</I>><i> for the reason error:undef +</I>><i>** Options were [{handler,connection_handler}] +</I>><i>** Request was [{socket,#Port<0.926>}, +</I>><i> {transport,ranch_tcp}, +</I>><i> {connection,keepalive}, +</I>><i> {pid,<0.491.0>}, +</I>><i> {method,<<"GET">>}, +</I>><i> {version,{1,1}}, +</I>><i> {peer,{{127,0,0,1},56630}}, +</I>><i> {host,<<"localhost">>}, +</I>><i> {host_info,undefined}, +</I>><i> {port,8080}, +</I>><i> {path,<<"/">>}, +</I>><i> {path_info,undefined}, +</I>><i> {qs,<<"encoding=text">>}, +</I>><i> {qs_vals,undefined}, +</I>><i> {fragment,<<>>}, +</I>><i> {bindings,[]}, +</I>><i> {headers,[{<<"upgrade">>,<<"websocket">>}, +</I>><i> {<<"connection">>,<<"Upgrade">>}, +</I>><i> {<<"host">>,<<"localhost:8080">>}, +</I>><i> {<<"origin">>,<<"<A HREF="http://www.websocket.org">http://www.websocket.org</A>">>}, +</I>><i> {<<"pragma">>,<<"no-cache">>}, +</I>><i> {<<"cache-control">>,<<"no-cache">>}, +</I>><i> {<<"sec-websocket-key">>, +</I>><i> <<"fEj/SOOcQgSKATOjhbNJBQ==">>}, +</I>><i> {<<"sec-websocket-version">>,<<"13">>}, +</I>><i> {<<"sec-websocket-extensions">>, +</I>><i> <<"x-webkit-deflate-frame">>}]}, +</I>><i> {p_headers,[{<<"connection">>,[<<"upgrade">>]}]}, +</I>><i> {cookies,undefined}, +</I>><i> {meta,[]}, +</I>><i> {body_state,waiting}, +</I>><i> {multipart,undefined}, +</I>><i> {buffer,<<>>}, +</I>><i> {resp_compress,false}, +</I>><i> {resp_state,waiting}, +</I>><i> {resp_headers,[]}, +</I>><i> {resp_body,<<>>}, +</I>><i> {onresponse,undefined}] +</I>><i>** Stacktrace: [{bullet_handler,init, +</I>><i> [{tcp,http}, +</I>><i> {http_req,#Port<0.926>,ranch_tcp,keepalive,<0.491.0>, +</I>><i> <<"GET">>, +</I>><i> {1,1}, +</I>><i> {{127,0,0,1},56630}, +</I>><i> <<"localhost">>,undefined,8080,<<"/">>, +</I>><i> undefined,<<"encoding=text">>,undefined,<<>>, +</I>><i> [], +</I>><i> [{<<"upgrade">>,<<"websocket">>}, +</I>><i> {<<"connection">>,<<"Upgrade">>}, +</I>><i> {<<"host">>,<<"localhost:8080">>}, +</I>><i> {<<"origin">>,<<"<A HREF="http://www.websocket.org">http://www.websocket.org</A>">>}, +</I>><i> {<<"pragma">>,<<"no-cache">>}, +</I>><i> {<<"cache-control">>,<<"no-cache">>}, +</I>><i> {<<"sec-websocket-key">>, +</I>><i> <<"fEj/SOOcQgSKATOjhbNJBQ==">>}, +</I>><i> {<<"sec-websocket-version">>,<<"13">>}, +</I>><i> {<<"sec-websocket-extensions">>, +</I>><i> <<"x-webkit-deflate-frame">>}], +</I>><i> [{<<"connection">>,[<<"upgrade">>]}], +</I>><i> +</I>><i>undefined,[],waiting,undefined,<<>>,false,waiting,[], +</I>><i> <<>>,undefined}, +</I>><i> [{handler,connection_handler}]], +</I>><i> []}, +</I>><i> {cowboy_handler,handler_init,4, +</I>><i> [{file,"src/cowboy_handler.erl"},{line,69}]}, +</I>><i> {cowboy_protocol,execute,4, +</I>><i> [{file,"src/cowboy_protocol.erl"},{line,514}]}] +</I>><i> +</I>><i>Can anyone see what might be throwing this off? I'd like to get a +</I>><i>minimal handler running before I attempt to add some logic. +</I>><i> +</I>><i>Thanks, +</I>><i>Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I> + + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000085.html">[99s-extend] Problems with Bullet +</A></li> + <LI>Next message: <A HREF="000086.html">[99s-extend] Heartbeat? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#83">[ date ]</a> + <a href="thread.html#83">[ thread ]</a> + <a href="subject.html#83">[ subject ]</a> + <a href="author.html#83">[ 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/_build/static/archives/extend/2013-April/000084.html b/_build/static/archives/extend/2013-April/000084.html new file mode 100644 index 00000000..36ba2a51 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000084.html @@ -0,0 +1,192 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Problems with Bullet + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Problems%20with%20Bullet&In-Reply-To=%3CCD8849A5.4807%25christopher.phillips%40turner.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="000082.html"> + <LINK REL="Next" HREF="000085.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Problems with Bullet</H1> + <B>Phillips, Christopher</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Problems%20with%20Bullet&In-Reply-To=%3CCD8849A5.4807%25christopher.phillips%40turner.com%3E" + TITLE="[99s-extend] Problems with Bullet">Christopher.Phillips at turner.com + </A><BR> + <I>Mon Apr 8 16:18:27 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000082.html">[99s-extend] Problems with Bullet +</A></li> + <LI>Next message: <A HREF="000085.html">[99s-extend] Problems with Bullet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#84">[ date ]</a> + <a href="thread.html#84">[ thread ]</a> + <a href="subject.html#84">[ subject ]</a> + <a href="author.html#84">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> *facepalm* Or that, yeah. Should have correlated the stack trace with +the error. Not used to seeing cowboy run as the app, not a dependency. + +On 4/8/13 10:08 AM, "Loïc Hoguin" <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: + +><i>Sounds like Bullet isn't in your path. Forgot -pa deps/*/ebin? +</I>><i> +</I>><i>On 04/08/2013 03:53 PM, Lee Sylvester wrote: +</I>>><i> Hi all, +</I>>><i> +</I>>><i> I'm currently having problems getting a websocket to connect to a +</I>>><i>simple bare bones Bullet handler. Unfortunately, I'm still quite an +</I>>><i>Erlang noob, so the stack traces tend to lead me in circles. I'm hoping +</I>>><i>this is obvious stuff to you Erlang pros :-) +</I>>><i> +</I>>><i> Given the below handler: +</I>>><i> +</I>>><i> init(_Transport, Req, _Opts, _Active) -> +</I>>><i> {ok, Req, undefined_state}. +</I>>><i> +</I>>><i> stream(Data, Req, State) -> +</I>>><i> {ok, Req, State}. +</I>>><i> +</I>>><i> info(Info, Req, State) -> +</I>>><i> {reply, Info, Req, State}. +</I>>><i> +</I>>><i> terminate(_Req, _State) -> +</I>>><i> ok. +</I>>><i> +</I>>><i> Connecting with a websocket throws the following error: +</I>>><i> +</I>>><i> =ERROR REPORT==== 8-Apr-2013::14:46:11 === +</I>>><i> ** Cowboy handler bullet_handler terminating in init/3 +</I>>><i> for the reason error:undef +</I>>><i> ** Options were [{handler,connection_handler}] +</I>>><i> ** Request was [{socket,#Port<0.926>}, +</I>>><i> {transport,ranch_tcp}, +</I>>><i> {connection,keepalive}, +</I>>><i> {pid,<0.491.0>}, +</I>>><i> {method,<<"GET">>}, +</I>>><i> {version,{1,1}}, +</I>>><i> {peer,{{127,0,0,1},56630}}, +</I>>><i> {host,<<"localhost">>}, +</I>>><i> {host_info,undefined}, +</I>>><i> {port,8080}, +</I>>><i> {path,<<"/">>}, +</I>>><i> {path_info,undefined}, +</I>>><i> {qs,<<"encoding=text">>}, +</I>>><i> {qs_vals,undefined}, +</I>>><i> {fragment,<<>>}, +</I>>><i> {bindings,[]}, +</I>>><i> {headers,[{<<"upgrade">>,<<"websocket">>}, +</I>>><i> {<<"connection">>,<<"Upgrade">>}, +</I>>><i> {<<"host">>,<<"localhost:8080">>}, +</I>>><i> +</I>>><i>{<<"origin">>,<<"<A HREF="http://www.websocket.org">http://www.websocket.org</A>">>}, +</I>>><i> {<<"pragma">>,<<"no-cache">>}, +</I>>><i> {<<"cache-control">>,<<"no-cache">>}, +</I>>><i> {<<"sec-websocket-key">>, +</I>>><i> <<"fEj/SOOcQgSKATOjhbNJBQ==">>}, +</I>>><i> {<<"sec-websocket-version">>,<<"13">>}, +</I>>><i> {<<"sec-websocket-extensions">>, +</I>>><i> <<"x-webkit-deflate-frame">>}]}, +</I>>><i> {p_headers,[{<<"connection">>,[<<"upgrade">>]}]}, +</I>>><i> {cookies,undefined}, +</I>>><i> {meta,[]}, +</I>>><i> {body_state,waiting}, +</I>>><i> {multipart,undefined}, +</I>>><i> {buffer,<<>>}, +</I>>><i> {resp_compress,false}, +</I>>><i> {resp_state,waiting}, +</I>>><i> {resp_headers,[]}, +</I>>><i> {resp_body,<<>>}, +</I>>><i> {onresponse,undefined}] +</I>>><i> ** Stacktrace: [{bullet_handler,init, +</I>>><i> [{tcp,http}, +</I>>><i> +</I>>><i>{http_req,#Port<0.926>,ranch_tcp,keepalive,<0.491.0>, +</I>>><i> <<"GET">>, +</I>>><i> {1,1}, +</I>>><i> {{127,0,0,1},56630}, +</I>>><i> <<"localhost">>,undefined,8080,<<"/">>, +</I>>><i> undefined,<<"encoding=text">>,undefined,<<>>, +</I>>><i> [], +</I>>><i> [{<<"upgrade">>,<<"websocket">>}, +</I>>><i> {<<"connection">>,<<"Upgrade">>}, +</I>>><i> {<<"host">>,<<"localhost:8080">>}, +</I>>><i> +</I>>><i>{<<"origin">>,<<"<A HREF="http://www.websocket.org">http://www.websocket.org</A>">>}, +</I>>><i> {<<"pragma">>,<<"no-cache">>}, +</I>>><i> {<<"cache-control">>,<<"no-cache">>}, +</I>>><i> {<<"sec-websocket-key">>, +</I>>><i> <<"fEj/SOOcQgSKATOjhbNJBQ==">>}, +</I>>><i> {<<"sec-websocket-version">>,<<"13">>}, +</I>>><i> {<<"sec-websocket-extensions">>, +</I>>><i> <<"x-webkit-deflate-frame">>}], +</I>>><i> [{<<"connection">>,[<<"upgrade">>]}], +</I>>><i> +</I>>><i>undefined,[],waiting,undefined,<<>>,false,waiting,[], +</I>>><i> <<>>,undefined}, +</I>>><i> [{handler,connection_handler}]], +</I>>><i> []}, +</I>>><i> {cowboy_handler,handler_init,4, +</I>>><i> [{file,"src/cowboy_handler.erl"},{line,69}]}, +</I>>><i> {cowboy_protocol,execute,4, +</I>>><i> [{file,"src/cowboy_protocol.erl"},{line,514}]}] +</I>>><i> +</I>>><i> Can anyone see what might be throwing this off? I'd like to get a +</I>>><i>minimal handler running before I attempt to add some logic. +</I>>><i> +</I>>><i> Thanks, +</I>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>><i> +</I>><i> +</I>><i> +</I>><i>-- +</I>><i>Loïc Hoguin +</I>><i>Erlang Cowboy +</I>><i>Nine Nines +</I>><i><A HREF="http://ninenines.eu">http://ninenines.eu</A> +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I> + + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000082.html">[99s-extend] Problems with Bullet +</A></li> + <LI>Next message: <A HREF="000085.html">[99s-extend] Problems with Bullet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#84">[ date ]</a> + <a href="thread.html#84">[ thread ]</a> + <a href="subject.html#84">[ subject ]</a> + <a href="author.html#84">[ 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/_build/static/archives/extend/2013-April/000085.html b/_build/static/archives/extend/2013-April/000085.html new file mode 100644 index 00000000..7d46c844 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000085.html @@ -0,0 +1,208 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Problems with Bullet + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Problems%20with%20Bullet&In-Reply-To=%3CA39F0108-E420-4FAB-A1A9-33C062509565%40gmail.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="000084.html"> + <LINK REL="Next" HREF="000083.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Problems with Bullet</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Problems%20with%20Bullet&In-Reply-To=%3CA39F0108-E420-4FAB-A1A9-33C062509565%40gmail.com%3E" + TITLE="[99s-extend] Problems with Bullet">lee.sylvester at gmail.com + </A><BR> + <I>Mon Apr 8 16:21:53 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000084.html">[99s-extend] Problems with Bullet +</A></li> + <LI>Next message: <A HREF="000083.html">[99s-extend] Problems with Bullet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#85">[ date ]</a> + <a href="thread.html#85">[ thread ]</a> + <a href="subject.html#85">[ subject ]</a> + <a href="author.html#85">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thanks guys, that was exactly the problem. I feel a little stupid :-) I use Rebar to compile my apps, but none of the three books I have on Erlang describe the config files in much detail. I probably have my entire setup wrong. + +Anyhow, it looks to be working, now :-) + +Thanks again, +Lee + + + +On 8 Apr 2013, at 15:18, "Phillips, Christopher" <<A HREF="https://lists.ninenines.eu/listinfo/extend">Christopher.Phillips at turner.com</A>> wrote: + +><i> *facepalm* Or that, yeah. Should have correlated the stack trace with +</I>><i> the error. Not used to seeing cowboy run as the app, not a dependency. +</I>><i> +</I>><i> On 4/8/13 10:08 AM, "Loïc Hoguin" <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: +</I>><i> +</I>>><i> Sounds like Bullet isn't in your path. Forgot -pa deps/*/ebin? +</I>>><i> +</I>>><i> On 04/08/2013 03:53 PM, Lee Sylvester wrote: +</I>>>><i> Hi all, +</I>>>><i> +</I>>>><i> I'm currently having problems getting a websocket to connect to a +</I>>>><i> simple bare bones Bullet handler. Unfortunately, I'm still quite an +</I>>>><i> Erlang noob, so the stack traces tend to lead me in circles. I'm hoping +</I>>>><i> this is obvious stuff to you Erlang pros :-) +</I>>>><i> +</I>>>><i> Given the below handler: +</I>>>><i> +</I>>>><i> init(_Transport, Req, _Opts, _Active) -> +</I>>>><i> {ok, Req, undefined_state}. +</I>>>><i> +</I>>>><i> stream(Data, Req, State) -> +</I>>>><i> {ok, Req, State}. +</I>>>><i> +</I>>>><i> info(Info, Req, State) -> +</I>>>><i> {reply, Info, Req, State}. +</I>>>><i> +</I>>>><i> terminate(_Req, _State) -> +</I>>>><i> ok. +</I>>>><i> +</I>>>><i> Connecting with a websocket throws the following error: +</I>>>><i> +</I>>>><i> =ERROR REPORT==== 8-Apr-2013::14:46:11 === +</I>>>><i> ** Cowboy handler bullet_handler terminating in init/3 +</I>>>><i> for the reason error:undef +</I>>>><i> ** Options were [{handler,connection_handler}] +</I>>>><i> ** Request was [{socket,#Port<0.926>}, +</I>>>><i> {transport,ranch_tcp}, +</I>>>><i> {connection,keepalive}, +</I>>>><i> {pid,<0.491.0>}, +</I>>>><i> {method,<<"GET">>}, +</I>>>><i> {version,{1,1}}, +</I>>>><i> {peer,{{127,0,0,1},56630}}, +</I>>>><i> {host,<<"localhost">>}, +</I>>>><i> {host_info,undefined}, +</I>>>><i> {port,8080}, +</I>>>><i> {path,<<"/">>}, +</I>>>><i> {path_info,undefined}, +</I>>>><i> {qs,<<"encoding=text">>}, +</I>>>><i> {qs_vals,undefined}, +</I>>>><i> {fragment,<<>>}, +</I>>>><i> {bindings,[]}, +</I>>>><i> {headers,[{<<"upgrade">>,<<"websocket">>}, +</I>>>><i> {<<"connection">>,<<"Upgrade">>}, +</I>>>><i> {<<"host">>,<<"localhost:8080">>}, +</I>>>><i> +</I>>>><i> {<<"origin">>,<<"<A HREF="http://www.websocket.org">http://www.websocket.org</A>">>}, +</I>>>><i> {<<"pragma">>,<<"no-cache">>}, +</I>>>><i> {<<"cache-control">>,<<"no-cache">>}, +</I>>>><i> {<<"sec-websocket-key">>, +</I>>>><i> <<"fEj/SOOcQgSKATOjhbNJBQ==">>}, +</I>>>><i> {<<"sec-websocket-version">>,<<"13">>}, +</I>>>><i> {<<"sec-websocket-extensions">>, +</I>>>><i> <<"x-webkit-deflate-frame">>}]}, +</I>>>><i> {p_headers,[{<<"connection">>,[<<"upgrade">>]}]}, +</I>>>><i> {cookies,undefined}, +</I>>>><i> {meta,[]}, +</I>>>><i> {body_state,waiting}, +</I>>>><i> {multipart,undefined}, +</I>>>><i> {buffer,<<>>}, +</I>>>><i> {resp_compress,false}, +</I>>>><i> {resp_state,waiting}, +</I>>>><i> {resp_headers,[]}, +</I>>>><i> {resp_body,<<>>}, +</I>>>><i> {onresponse,undefined}] +</I>>>><i> ** Stacktrace: [{bullet_handler,init, +</I>>>><i> [{tcp,http}, +</I>>>><i> +</I>>>><i> {http_req,#Port<0.926>,ranch_tcp,keepalive,<0.491.0>, +</I>>>><i> <<"GET">>, +</I>>>><i> {1,1}, +</I>>>><i> {{127,0,0,1},56630}, +</I>>>><i> <<"localhost">>,undefined,8080,<<"/">>, +</I>>>><i> undefined,<<"encoding=text">>,undefined,<<>>, +</I>>>><i> [], +</I>>>><i> [{<<"upgrade">>,<<"websocket">>}, +</I>>>><i> {<<"connection">>,<<"Upgrade">>}, +</I>>>><i> {<<"host">>,<<"localhost:8080">>}, +</I>>>><i> +</I>>>><i> {<<"origin">>,<<"<A HREF="http://www.websocket.org">http://www.websocket.org</A>">>}, +</I>>>><i> {<<"pragma">>,<<"no-cache">>}, +</I>>>><i> {<<"cache-control">>,<<"no-cache">>}, +</I>>>><i> {<<"sec-websocket-key">>, +</I>>>><i> <<"fEj/SOOcQgSKATOjhbNJBQ==">>}, +</I>>>><i> {<<"sec-websocket-version">>,<<"13">>}, +</I>>>><i> {<<"sec-websocket-extensions">>, +</I>>>><i> <<"x-webkit-deflate-frame">>}], +</I>>>><i> [{<<"connection">>,[<<"upgrade">>]}], +</I>>>><i> +</I>>>><i> undefined,[],waiting,undefined,<<>>,false,waiting,[], +</I>>>><i> <<>>,undefined}, +</I>>>><i> [{handler,connection_handler}]], +</I>>>><i> []}, +</I>>>><i> {cowboy_handler,handler_init,4, +</I>>>><i> [{file,"src/cowboy_handler.erl"},{line,69}]}, +</I>>>><i> {cowboy_protocol,execute,4, +</I>>>><i> [{file,"src/cowboy_protocol.erl"},{line,514}]}] +</I>>>><i> +</I>>>><i> Can anyone see what might be throwing this off? I'd like to get a +</I>>>><i> minimal handler running before I attempt to add some logic. +</I>>>><i> +</I>>>><i> Thanks, +</I>>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>>><i> +</I>>><i> +</I>>><i> +</I>>><i> -- +</I>>><i> Loïc Hoguin +</I>>><i> Erlang Cowboy +</I>>><i> Nine Nines +</I>>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000084.html">[99s-extend] Problems with Bullet +</A></li> + <LI>Next message: <A HREF="000083.html">[99s-extend] Problems with Bullet +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#85">[ date ]</a> + <a href="thread.html#85">[ thread ]</a> + <a href="subject.html#85">[ subject ]</a> + <a href="author.html#85">[ 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/_build/static/archives/extend/2013-April/000086.html b/_build/static/archives/extend/2013-April/000086.html new file mode 100644 index 00000000..f17e2a4b --- /dev/null +++ b/_build/static/archives/extend/2013-April/000086.html @@ -0,0 +1,66 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Heartbeat? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Heartbeat%3F&In-Reply-To=%3CDC437291-FAB7-4E9D-AAAA-EC8B5E755A20%40gmail.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="000083.html"> + <LINK REL="Next" HREF="000088.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Heartbeat?</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Heartbeat%3F&In-Reply-To=%3CDC437291-FAB7-4E9D-AAAA-EC8B5E755A20%40gmail.com%3E" + TITLE="[99s-extend] Heartbeat?">lee.sylvester at gmail.com + </A><BR> + <I>Wed Apr 10 13:47:45 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000083.html">[99s-extend] Problems with Bullet +</A></li> + <LI>Next message: <A HREF="000088.html">[99s-extend] Heartbeat? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#86">[ date ]</a> + <a href="thread.html#86">[ thread ]</a> + <a href="subject.html#86">[ subject ]</a> + <a href="author.html#86">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hey guys, + +So, my bullet websockets are going great. However, I have a question. At present, if I don't send any data to or from my websockets for a while, the connection closes after about 10 - 20 seconds. Therefore, should I send a heartbeat to the client from Erlang to keep this open? The websockets are for user to user messaging, so it's possible that large periods of inactivity could occur. + +Thanks, +Lee +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000083.html">[99s-extend] Problems with Bullet +</A></li> + <LI>Next message: <A HREF="000088.html">[99s-extend] Heartbeat? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#86">[ date ]</a> + <a href="thread.html#86">[ thread ]</a> + <a href="subject.html#86">[ subject ]</a> + <a href="author.html#86">[ 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/_build/static/archives/extend/2013-April/000087.html b/_build/static/archives/extend/2013-April/000087.html new file mode 100644 index 00000000..b024dbf3 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000087.html @@ -0,0 +1,78 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy and chromium + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C90FA9B10-201C-469E-AF79-749CF56160F1%40gmail.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="000092.html"> + <LINK REL="Next" HREF="000089.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy and chromium</H1> + <B>Sasa Juric</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C90FA9B10-201C-469E-AF79-749CF56160F1%40gmail.com%3E" + TITLE="[99s-extend] cowboy and chromium">sasa.juric at gmail.com + </A><BR> + <I>Wed Apr 10 14:00:47 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000092.html">[99s-extend] Heartbeat? +</A></li> + <LI>Next message: <A HREF="000089.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#87">[ date ]</a> + <a href="thread.html#87">[ thread ]</a> + <a href="subject.html#87">[ subject ]</a> + <a href="author.html#87">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, + +I have recently in my production system replaced mochiweb with cowboy. The server generally works fine, except for a bizarre behavior which I cannot quite explain, so I post here, hoping to get some pointers. + +After replacing mochiweb with cowboy, I noticed that in chromium (other major browsers work fine) often (but not always) a request lasts a little more than a minute. Further inspection in <A HREF="chrome://net-internals">chrome://net-internals</A> showed that browser tries to send a request, times out after 60 sec, retries and then succeeds immediately. The key point is that it doesn't happen always. First couple of requests work fine, then all of a sudden one doesn't work. At the same time requests from other browsers (including chrome) on the same machine work fine. + +If I revert to mochiweb, the problem disappears. Other than web server related code, everything else is the same: the rest of my code, the server setup etc... In addition, I return same responses and headers in both versions. + +After many attempts and failures, I might have worked around the issue. Namely, I included <<"connection">>, <<"close">> in all responses. After this change, it seems that long requests are not occurring. In any case, I can't reproduce it anymore, whereas before the change I could have reproduce it easily. + +However, I'm not sure if I have really resolved the issue, I'm also not happy with connection closes since it degrades performance. And finally, I'm not sure if I quite understand the problem. +The only theory I have is that due to keep-alive, chromium holds the connection, while cowboy closes it (I read somewhere that hardcoded timeout is 5 seconds, right?). In this case it might happen that chromium sends a request to a non existing socket and then hangs for a minute, waiting for the response which never arrives. +This might further be amplified by the fact that in production, between browser and cowboy, there is a proxy/load balancer, so maybe load balancer still holds the connection despite the fact that server had closed it. + +This is the only theory I currently have, and I would like to hear if you guys have some other idea or any kind of helpful pointer? + +Thank you very much in advance and best regards, +Sasa +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000092.html">[99s-extend] Heartbeat? +</A></li> + <LI>Next message: <A HREF="000089.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#87">[ date ]</a> + <a href="thread.html#87">[ thread ]</a> + <a href="subject.html#87">[ subject ]</a> + <a href="author.html#87">[ 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/_build/static/archives/extend/2013-April/000088.html b/_build/static/archives/extend/2013-April/000088.html new file mode 100644 index 00000000..0ba2bb7e --- /dev/null +++ b/_build/static/archives/extend/2013-April/000088.html @@ -0,0 +1,75 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Heartbeat? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Heartbeat%3F&In-Reply-To=%3C51657962.8020009%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="000086.html"> + <LINK REL="Next" HREF="000092.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Heartbeat?</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Heartbeat%3F&In-Reply-To=%3C51657962.8020009%40ninenines.eu%3E" + TITLE="[99s-extend] Heartbeat?">essen at ninenines.eu + </A><BR> + <I>Wed Apr 10 16:38:26 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000086.html">[99s-extend] Heartbeat? +</A></li> + <LI>Next message: <A HREF="000092.html">[99s-extend] Heartbeat? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#88">[ date ]</a> + <a href="thread.html#88">[ thread ]</a> + <a href="subject.html#88">[ subject ]</a> + <a href="author.html#88">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 04/10/2013 01:47 PM, Lee Sylvester wrote: +><i> Hey guys, +</I>><i> +</I>><i> So, my bullet websockets are going great. However, I have a question. At present, if I don't send any data to or from my websockets for a while, the connection closes after about 10 - 20 seconds. Therefore, should I send a heartbeat to the client from Erlang to keep this open? The websockets are for user to user messaging, so it's possible that large periods of inactivity could occur. +</I> +Send one from the client if you want it to scale. Bullet provides you +with one callback that you can use to send anything. If you're using +JSON then sending {} is generally enough. + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000086.html">[99s-extend] Heartbeat? +</A></li> + <LI>Next message: <A HREF="000092.html">[99s-extend] Heartbeat? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#88">[ date ]</a> + <a href="thread.html#88">[ thread ]</a> + <a href="subject.html#88">[ subject ]</a> + <a href="author.html#88">[ 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/_build/static/archives/extend/2013-April/000089.html b/_build/static/archives/extend/2013-April/000089.html new file mode 100644 index 00000000..dad65559 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000089.html @@ -0,0 +1,86 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy and chromium + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C51657A11.7070902%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="000087.html"> + <LINK REL="Next" HREF="000090.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy and chromium</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C51657A11.7070902%40ninenines.eu%3E" + TITLE="[99s-extend] cowboy and chromium">essen at ninenines.eu + </A><BR> + <I>Wed Apr 10 16:41:21 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000087.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000090.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#89">[ date ]</a> + <a href="thread.html#89">[ thread ]</a> + <a href="subject.html#89">[ subject ]</a> + <a href="author.html#89">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 04/10/2013 02:00 PM, Sasa Juric wrote: +><i> Hi, +</I>><i> +</I>><i> I have recently in my production system replaced mochiweb with cowboy. The server generally works fine, except for a bizarre behavior which I cannot quite explain, so I post here, hoping to get some pointers. +</I>><i> +</I>><i> After replacing mochiweb with cowboy, I noticed that in chromium (other major browsers work fine) often (but not always) a request lasts a little more than a minute. Further inspection in <A HREF="chrome://net-internals">chrome://net-internals</A> showed that browser tries to send a request, times out after 60 sec, retries and then succeeds immediately. The key point is that it doesn't happen always. First couple of requests work fine, then all of a sudden one doesn't work. At the same time requests from other browsers (including chrome) on the same machine work fine. +</I>><i> +</I>><i> If I revert to mochiweb, the problem disappears. Other than web server related code, everything else is the same: the rest of my code, the server setup etc... In addition, I return same responses and headers in both versions. +</I>><i> +</I>><i> After many attempts and failures, I might have worked around the issue. Namely, I included <<"connection">>, <<"close">> in all responses. After this change, it seems that long requests are not occurring. In any case, I can't reproduce it anymore, whereas before the change I could have reproduce it easily. +</I>><i> +</I>><i> However, I'm not sure if I have really resolved the issue, I'm also not happy with connection closes since it degrades performance. And finally, I'm not sure if I quite understand the problem. +</I>><i> The only theory I have is that due to keep-alive, chromium holds the connection, while cowboy closes it (I read somewhere that hardcoded timeout is 5 seconds, right?). In this case it might happen that chromium sends a request to a non existing socket and then hangs for a minute, waiting for the response which never arrives. +</I>><i> This might further be amplified by the fact that in production, between browser and cowboy, there is a proxy/load balancer, so maybe load balancer still holds the connection despite the fact that server had closed it. +</I>><i> +</I>><i> This is the only theory I currently have, and I would like to hear if you guys have some other idea or any kind of helpful pointer? +</I> +Haven't seen this happen on plain Cowboy. The proxy might be the +culprit. See if you can reproduce without the proxy. + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000087.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000090.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#89">[ date ]</a> + <a href="thread.html#89">[ thread ]</a> + <a href="subject.html#89">[ subject ]</a> + <a href="author.html#89">[ 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/_build/static/archives/extend/2013-April/000090.html b/_build/static/archives/extend/2013-April/000090.html new file mode 100644 index 00000000..a40dcac3 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000090.html @@ -0,0 +1,97 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy and chromium + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C3CACD966-2058-4ABF-A819-AE127BE964D7%40gmail.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="000089.html"> + <LINK REL="Next" HREF="000091.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy and chromium</H1> + <B>Sasa Juric</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C3CACD966-2058-4ABF-A819-AE127BE964D7%40gmail.com%3E" + TITLE="[99s-extend] cowboy and chromium">sasa.juric at gmail.com + </A><BR> + <I>Wed Apr 10 16:50:31 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000089.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000091.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#90">[ date ]</a> + <a href="thread.html#90">[ thread ]</a> + <a href="subject.html#90">[ subject ]</a> + <a href="author.html#90">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>I agree with you. In addition, I can't reproduce without the proxy, which confirms the suspicion. + +Looking at the code of mochiweb which I was using, the connection timeout is set to 5 minutes. +The other factor, which I can confirm is that when the server terminates the connection, the proxy doesn't forward this to the client. Hence, the client and proxy probably "think" that connection is still active, and try to reuse it, but this doesn't work until timeout. +Other browsers probably can gracefully handle this situation, but for some reason chromium is stuck to 60 seconds and after retry it presumably opens new connection and succeeds. + +Question: can I configure keep-alive timeout in Cowboy? + + +On Apr 10, 2013, at 4:41 PM, Loïc Hoguin wrote: + +><i> On 04/10/2013 02:00 PM, Sasa Juric wrote: +</I>>><i> Hi, +</I>>><i> +</I>>><i> I have recently in my production system replaced mochiweb with cowboy. The server generally works fine, except for a bizarre behavior which I cannot quite explain, so I post here, hoping to get some pointers. +</I>>><i> +</I>>><i> After replacing mochiweb with cowboy, I noticed that in chromium (other major browsers work fine) often (but not always) a request lasts a little more than a minute. Further inspection in <A HREF="chrome://net-internals">chrome://net-internals</A> showed that browser tries to send a request, times out after 60 sec, retries and then succeeds immediately. The key point is that it doesn't happen always. First couple of requests work fine, then all of a sudden one doesn't work. At the same time requests from other browsers (including chrome) on the same machine work fine. +</I>>><i> +</I>>><i> If I revert to mochiweb, the problem disappears. Other than web server related code, everything else is the same: the rest of my code, the server setup etc... In addition, I return same responses and headers in both versions. +</I>>><i> +</I>>><i> After many attempts and failures, I might have worked around the issue. Namely, I included <<"connection">>, <<"close">> in all responses. After this change, it seems that long requests are not occurring. In any case, I can't reproduce it anymore, whereas before the change I could have reproduce it easily. +</I>>><i> +</I>>><i> However, I'm not sure if I have really resolved the issue, I'm also not happy with connection closes since it degrades performance. And finally, I'm not sure if I quite understand the problem. +</I>>><i> The only theory I have is that due to keep-alive, chromium holds the connection, while cowboy closes it (I read somewhere that hardcoded timeout is 5 seconds, right?). In this case it might happen that chromium sends a request to a non existing socket and then hangs for a minute, waiting for the response which never arrives. +</I>>><i> This might further be amplified by the fact that in production, between browser and cowboy, there is a proxy/load balancer, so maybe load balancer still holds the connection despite the fact that server had closed it. +</I>>><i> +</I>>><i> This is the only theory I currently have, and I would like to hear if you guys have some other idea or any kind of helpful pointer? +</I>><i> +</I>><i> Haven't seen this happen on plain Cowboy. The proxy might be the culprit. See if you can reproduce without the proxy. +</I>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> Erlang Cowboy +</I>><i> Nine Nines +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000089.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000091.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#90">[ date ]</a> + <a href="thread.html#90">[ thread ]</a> + <a href="subject.html#90">[ subject ]</a> + <a href="author.html#90">[ 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/_build/static/archives/extend/2013-April/000091.html b/_build/static/archives/extend/2013-April/000091.html new file mode 100644 index 00000000..0e8d39ec --- /dev/null +++ b/_build/static/archives/extend/2013-April/000091.html @@ -0,0 +1,107 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy and chromium + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C51657C86.2060800%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="000090.html"> + <LINK REL="Next" HREF="000093.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy and chromium</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C51657C86.2060800%40ninenines.eu%3E" + TITLE="[99s-extend] cowboy and chromium">essen at ninenines.eu + </A><BR> + <I>Wed Apr 10 16:51:50 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000090.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000093.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#91">[ date ]</a> + <a href="thread.html#91">[ thread ]</a> + <a href="subject.html#91">[ subject ]</a> + <a href="author.html#91">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'timeout' protocol option, in milliseconds. + +On 04/10/2013 04:50 PM, Sasa Juric wrote: +><i> I agree with you. In addition, I can't reproduce without the proxy, which confirms the suspicion. +</I>><i> +</I>><i> Looking at the code of mochiweb which I was using, the connection timeout is set to 5 minutes. +</I>><i> The other factor, which I can confirm is that when the server terminates the connection, the proxy doesn't forward this to the client. Hence, the client and proxy probably "think" that connection is still active, and try to reuse it, but this doesn't work until timeout. +</I>><i> Other browsers probably can gracefully handle this situation, but for some reason chromium is stuck to 60 seconds and after retry it presumably opens new connection and succeeds. +</I>><i> +</I>><i> Question: can I configure keep-alive timeout in Cowboy? +</I>><i> +</I>><i> +</I>><i> On Apr 10, 2013, at 4:41 PM, Loïc Hoguin wrote: +</I>><i> +</I>>><i> On 04/10/2013 02:00 PM, Sasa Juric wrote: +</I>>>><i> Hi, +</I>>>><i> +</I>>>><i> I have recently in my production system replaced mochiweb with cowboy. The server generally works fine, except for a bizarre behavior which I cannot quite explain, so I post here, hoping to get some pointers. +</I>>>><i> +</I>>>><i> After replacing mochiweb with cowboy, I noticed that in chromium (other major browsers work fine) often (but not always) a request lasts a little more than a minute. Further inspection in <A HREF="chrome://net-internals">chrome://net-internals</A> showed that browser tries to send a request, times out after 60 sec, retries and then succeeds immediately. The key point is that it doesn't happen always. First couple of requests work fine, then all of a sudden one doesn't work. At the same time requests from other browsers (including chrome) on the same machine work fine. +</I>>>><i> +</I>>>><i> If I revert to mochiweb, the problem disappears. Other than web server related code, everything else is the same: the rest of my code, the server setup etc... In addition, I return same responses and headers in both versions. +</I>>>><i> +</I>>>><i> After many attempts and failures, I might have worked around the issue. Namely, I included <<"connection">>, <<"close">> in all responses. After this change, it seems that long requests are not occurring. In any case, I can't reproduce it anymore, whereas before the change I could have reproduce it easily. +</I>>>><i> +</I>>>><i> However, I'm not sure if I have really resolved the issue, I'm also not happy with connection closes since it degrades performance. And finally, I'm not sure if I quite understand the problem. +</I>>>><i> The only theory I have is that due to keep-alive, chromium holds the connection, while cowboy closes it (I read somewhere that hardcoded timeout is 5 seconds, right?). In this case it might happen that chromium sends a request to a non existing socket and then hangs for a minute, waiting for the response which never arrives. +</I>>>><i> This might further be amplified by the fact that in production, between browser and cowboy, there is a proxy/load balancer, so maybe load balancer still holds the connection despite the fact that server had closed it. +</I>>>><i> +</I>>>><i> This is the only theory I currently have, and I would like to hear if you guys have some other idea or any kind of helpful pointer? +</I>>><i> +</I>>><i> Haven't seen this happen on plain Cowboy. The proxy might be the culprit. See if you can reproduce without the proxy. +</I>>><i> +</I>>><i> -- +</I>>><i> Loïc Hoguin +</I>>><i> Erlang Cowboy +</I>>><i> Nine Nines +</I>>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I> + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000090.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000093.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#91">[ date ]</a> + <a href="thread.html#91">[ thread ]</a> + <a href="subject.html#91">[ subject ]</a> + <a href="author.html#91">[ 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/_build/static/archives/extend/2013-April/000092.html b/_build/static/archives/extend/2013-April/000092.html new file mode 100644 index 00000000..7df4cb55 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000092.html @@ -0,0 +1,83 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Heartbeat? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Heartbeat%3F&In-Reply-To=%3C2499D410-A700-41A3-A926-F721CC092600%40gmail.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="000088.html"> + <LINK REL="Next" HREF="000087.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Heartbeat?</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Heartbeat%3F&In-Reply-To=%3C2499D410-A700-41A3-A926-F721CC092600%40gmail.com%3E" + TITLE="[99s-extend] Heartbeat?">lee.sylvester at gmail.com + </A><BR> + <I>Wed Apr 10 16:53:24 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000088.html">[99s-extend] Heartbeat? +</A></li> + <LI>Next message: <A HREF="000087.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#92">[ date ]</a> + <a href="thread.html#92">[ thread ]</a> + <a href="subject.html#92">[ subject ]</a> + <a href="author.html#92">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Ahh, thank you. + +Regards, +Lee + + + +On 10 Apr 2013, at 15:38, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: + +><i> On 04/10/2013 01:47 PM, Lee Sylvester wrote: +</I>>><i> Hey guys, +</I>>><i> +</I>>><i> So, my bullet websockets are going great. However, I have a question. At present, if I don't send any data to or from my websockets for a while, the connection closes after about 10 - 20 seconds. Therefore, should I send a heartbeat to the client from Erlang to keep this open? The websockets are for user to user messaging, so it's possible that large periods of inactivity could occur. +</I>><i> +</I>><i> Send one from the client if you want it to scale. Bullet provides you with one callback that you can use to send anything. If you're using JSON then sending {} is generally enough. +</I>><i> +</I>><i> -- +</I>><i> Loïc Hoguin +</I>><i> Erlang Cowboy +</I>><i> Nine Nines +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000088.html">[99s-extend] Heartbeat? +</A></li> + <LI>Next message: <A HREF="000087.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#92">[ date ]</a> + <a href="thread.html#92">[ thread ]</a> + <a href="subject.html#92">[ subject ]</a> + <a href="author.html#92">[ 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/_build/static/archives/extend/2013-April/000093.html b/_build/static/archives/extend/2013-April/000093.html new file mode 100644 index 00000000..25544b4e --- /dev/null +++ b/_build/static/archives/extend/2013-April/000093.html @@ -0,0 +1,120 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy and chromium + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3CAE3B3DE1-BEC0-4265-92EC-9D14EB4E0D59%40gmail.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="000091.html"> + <LINK REL="Next" HREF="000094.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy and chromium</H1> + <B>Sasa Juric</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3CAE3B3DE1-BEC0-4265-92EC-9D14EB4E0D59%40gmail.com%3E" + TITLE="[99s-extend] cowboy and chromium">sasa.juric at gmail.com + </A><BR> + <I>Wed Apr 10 16:56:08 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000091.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000094.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#93">[ date ]</a> + <a href="thread.html#93">[ thread ]</a> + <a href="subject.html#93">[ subject ]</a> + <a href="author.html#93">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thanks! + +I was looking at the option, but was confused by description which states: +Time in milliseconds a client has to send the full request line and headers. + +I'll give it a try and see how it works. + +Best regards, +Sasa + +On Apr 10, 2013, at 4:51 PM, Loïc Hoguin wrote: + +><i> 'timeout' protocol option, in milliseconds. +</I>><i> +</I>><i> On 04/10/2013 04:50 PM, Sasa Juric wrote: +</I>>><i> I agree with you. In addition, I can't reproduce without the proxy, which confirms the suspicion. +</I>>><i> +</I>>><i> Looking at the code of mochiweb which I was using, the connection timeout is set to 5 minutes. +</I>>><i> The other factor, which I can confirm is that when the server terminates the connection, the proxy doesn't forward this to the client. Hence, the client and proxy probably "think" that connection is still active, and try to reuse it, but this doesn't work until timeout. +</I>>><i> Other browsers probably can gracefully handle this situation, but for some reason chromium is stuck to 60 seconds and after retry it presumably opens new connection and succeeds. +</I>>><i> +</I>>><i> Question: can I configure keep-alive timeout in Cowboy? +</I>>><i> +</I>>><i> +</I>>><i> On Apr 10, 2013, at 4:41 PM, Loïc Hoguin wrote: +</I>>><i> +</I>>>><i> On 04/10/2013 02:00 PM, Sasa Juric wrote: +</I>>>>><i> Hi, +</I>>>>><i> +</I>>>>><i> I have recently in my production system replaced mochiweb with cowboy. The server generally works fine, except for a bizarre behavior which I cannot quite explain, so I post here, hoping to get some pointers. +</I>>>>><i> +</I>>>>><i> After replacing mochiweb with cowboy, I noticed that in chromium (other major browsers work fine) often (but not always) a request lasts a little more than a minute. Further inspection in <A HREF="chrome://net-internals">chrome://net-internals</A> showed that browser tries to send a request, times out after 60 sec, retries and then succeeds immediately. The key point is that it doesn't happen always. First couple of requests work fine, then all of a sudden one doesn't work. At the same time requests from other browsers (including chrome) on the same machine work fine. +</I>>>>><i> +</I>>>>><i> If I revert to mochiweb, the problem disappears. Other than web server related code, everything else is the same: the rest of my code, the server setup etc... In addition, I return same responses and headers in both versions. +</I>>>>><i> +</I>>>>><i> After many attempts and failures, I might have worked around the issue. Namely, I included <<"connection">>, <<"close">> in all responses. After this change, it seems that long requests are not occurring. In any case, I can't reproduce it anymore, whereas before the change I could have reproduce it easily. +</I>>>>><i> +</I>>>>><i> However, I'm not sure if I have really resolved the issue, I'm also not happy with connection closes since it degrades performance. And finally, I'm not sure if I quite understand the problem. +</I>>>>><i> The only theory I have is that due to keep-alive, chromium holds the connection, while cowboy closes it (I read somewhere that hardcoded timeout is 5 seconds, right?). In this case it might happen that chromium sends a request to a non existing socket and then hangs for a minute, waiting for the response which never arrives. +</I>>>>><i> This might further be amplified by the fact that in production, between browser and cowboy, there is a proxy/load balancer, so maybe load balancer still holds the connection despite the fact that server had closed it. +</I>>>>><i> +</I>>>>><i> This is the only theory I currently have, and I would like to hear if you guys have some other idea or any kind of helpful pointer? +</I>>>><i> +</I>>>><i> Haven't seen this happen on plain Cowboy. The proxy might be the culprit. See if you can reproduce without the proxy. +</I>>>><i> +</I>>>><i> -- +</I>>>><i> Loïc Hoguin +</I>>>><i> Erlang Cowboy +</I>>>><i> Nine Nines +</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> Erlang Cowboy +</I>><i> Nine Nines +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000091.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000094.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#93">[ date ]</a> + <a href="thread.html#93">[ thread ]</a> + <a href="subject.html#93">[ subject ]</a> + <a href="author.html#93">[ 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/_build/static/archives/extend/2013-April/000094.html b/_build/static/archives/extend/2013-April/000094.html new file mode 100644 index 00000000..48a3dac6 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000094.html @@ -0,0 +1,132 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy and chromium + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C51657EBA.7050506%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="000093.html"> + <LINK REL="Next" HREF="000095.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy and chromium</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C51657EBA.7050506%40ninenines.eu%3E" + TITLE="[99s-extend] cowboy and chromium">essen at ninenines.eu + </A><BR> + <I>Wed Apr 10 17:01:14 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000093.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000095.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#94">[ date ]</a> + <a href="thread.html#94">[ thread ]</a> + <a href="subject.html#94">[ subject ]</a> + <a href="author.html#94">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Means it's not a read timeout, but a timeout for the whole request up to +and excluding the body (so an intentionally slow client will get +disconnected at 5s). + +On 04/10/2013 04:56 PM, Sasa Juric wrote: +><i> Thanks! +</I>><i> +</I>><i> I was looking at the option, but was confused by description which states: +</I>><i> Time in milliseconds a client has to send the full request line and headers. +</I>><i> +</I>><i> I'll give it a try and see how it works. +</I>><i> +</I>><i> Best regards, +</I>><i> Sasa +</I>><i> +</I>><i> On Apr 10, 2013, at 4:51 PM, Loïc Hoguin wrote: +</I>><i> +</I>>><i> 'timeout' protocol option, in milliseconds. +</I>>><i> +</I>>><i> On 04/10/2013 04:50 PM, Sasa Juric wrote: +</I>>>><i> I agree with you. In addition, I can't reproduce without the proxy, which confirms the suspicion. +</I>>>><i> +</I>>>><i> Looking at the code of mochiweb which I was using, the connection timeout is set to 5 minutes. +</I>>>><i> The other factor, which I can confirm is that when the server terminates the connection, the proxy doesn't forward this to the client. Hence, the client and proxy probably "think" that connection is still active, and try to reuse it, but this doesn't work until timeout. +</I>>>><i> Other browsers probably can gracefully handle this situation, but for some reason chromium is stuck to 60 seconds and after retry it presumably opens new connection and succeeds. +</I>>>><i> +</I>>>><i> Question: can I configure keep-alive timeout in Cowboy? +</I>>>><i> +</I>>>><i> +</I>>>><i> On Apr 10, 2013, at 4:41 PM, Loïc Hoguin wrote: +</I>>>><i> +</I>>>>><i> On 04/10/2013 02:00 PM, Sasa Juric wrote: +</I>>>>>><i> Hi, +</I>>>>>><i> +</I>>>>>><i> I have recently in my production system replaced mochiweb with cowboy. The server generally works fine, except for a bizarre behavior which I cannot quite explain, so I post here, hoping to get some pointers. +</I>>>>>><i> +</I>>>>>><i> After replacing mochiweb with cowboy, I noticed that in chromium (other major browsers work fine) often (but not always) a request lasts a little more than a minute. Further inspection in <A HREF="chrome://net-internals">chrome://net-internals</A> showed that browser tries to send a request, times out after 60 sec, retries and then succeeds immediately. The key point is that it doesn't happen always. First couple of requests work fine, then all of a sudden one doesn't work. At the same time requests from other browsers (including chrome) on the same machine work fine. +</I>>>>>><i> +</I>>>>>><i> If I revert to mochiweb, the problem disappears. Other than web server related code, everything else is the same: the rest of my code, the server setup etc... In addition, I return same responses and headers in both versions. +</I>>>>>><i> +</I>>>>>><i> After many attempts and failures, I might have worked around the issue. Namely, I included <<"connection">>, <<"close">> in all responses. After this change, it seems that long requests are not occurring. In any case, I can't reproduce it anymore, whereas before the change I could have reproduce it easily. +</I>>>>>><i> +</I>>>>>><i> However, I'm not sure if I have really resolved the issue, I'm also not happy with connection closes since it degrades performance. And finally, I'm not sure if I quite understand the problem. +</I>>>>>><i> The only theory I have is that due to keep-alive, chromium holds the connection, while cowboy closes it (I read somewhere that hardcoded timeout is 5 seconds, right?). In this case it might happen that chromium sends a request to a non existing socket and then hangs for a minute, waiting for the response which never arrives. +</I>>>>>><i> This might further be amplified by the fact that in production, between browser and cowboy, there is a proxy/load balancer, so maybe load balancer still holds the connection despite the fact that server had closed it. +</I>>>>>><i> +</I>>>>>><i> This is the only theory I currently have, and I would like to hear if you guys have some other idea or any kind of helpful pointer? +</I>>>>><i> +</I>>>>><i> Haven't seen this happen on plain Cowboy. The proxy might be the culprit. See if you can reproduce without the proxy. +</I>>>>><i> +</I>>>>><i> -- +</I>>>>><i> Loïc Hoguin +</I>>>>><i> Erlang Cowboy +</I>>>>><i> Nine Nines +</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> Erlang Cowboy +</I>>><i> Nine Nines +</I>>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I> + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000093.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000095.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#94">[ date ]</a> + <a href="thread.html#94">[ thread ]</a> + <a href="subject.html#94">[ subject ]</a> + <a href="author.html#94">[ 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/_build/static/archives/extend/2013-April/000095.html b/_build/static/archives/extend/2013-April/000095.html new file mode 100644 index 00000000..1e8cc343 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000095.html @@ -0,0 +1,137 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy and chromium + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3CE7866B20-0B8D-4192-8956-B5F4AD820FA9%40gmail.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="000094.html"> + <LINK REL="Next" HREF="000096.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy and chromium</H1> + <B>Sasa Juric</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3CE7866B20-0B8D-4192-8956-B5F4AD820FA9%40gmail.com%3E" + TITLE="[99s-extend] cowboy and chromium">sasa.juric at gmail.com + </A><BR> + <I>Wed Apr 10 17:05:51 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000094.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000096.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#95">[ date ]</a> + <a href="thread.html#95">[ thread ]</a> + <a href="subject.html#95">[ subject ]</a> + <a href="author.html#95">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Ok, just to make sure I understand: +When I serve a request, and the connection is not closed due to keep-alive, will this timeout also apply? + + +On Apr 10, 2013, at 5:01 PM, Loïc Hoguin wrote: + +><i> Means it's not a read timeout, but a timeout for the whole request up to and excluding the body (so an intentionally slow client will get disconnected at 5s). +</I>><i> +</I>><i> On 04/10/2013 04:56 PM, Sasa Juric wrote: +</I>>><i> Thanks! +</I>>><i> +</I>>><i> I was looking at the option, but was confused by description which states: +</I>>><i> Time in milliseconds a client has to send the full request line and headers. +</I>>><i> +</I>>><i> I'll give it a try and see how it works. +</I>>><i> +</I>>><i> Best regards, +</I>>><i> Sasa +</I>>><i> +</I>>><i> On Apr 10, 2013, at 4:51 PM, Loïc Hoguin wrote: +</I>>><i> +</I>>>><i> 'timeout' protocol option, in milliseconds. +</I>>>><i> +</I>>>><i> On 04/10/2013 04:50 PM, Sasa Juric wrote: +</I>>>>><i> I agree with you. In addition, I can't reproduce without the proxy, which confirms the suspicion. +</I>>>>><i> +</I>>>>><i> Looking at the code of mochiweb which I was using, the connection timeout is set to 5 minutes. +</I>>>>><i> The other factor, which I can confirm is that when the server terminates the connection, the proxy doesn't forward this to the client. Hence, the client and proxy probably "think" that connection is still active, and try to reuse it, but this doesn't work until timeout. +</I>>>>><i> Other browsers probably can gracefully handle this situation, but for some reason chromium is stuck to 60 seconds and after retry it presumably opens new connection and succeeds. +</I>>>>><i> +</I>>>>><i> Question: can I configure keep-alive timeout in Cowboy? +</I>>>>><i> +</I>>>>><i> +</I>>>>><i> On Apr 10, 2013, at 4:41 PM, Loïc Hoguin wrote: +</I>>>>><i> +</I>>>>>><i> On 04/10/2013 02:00 PM, Sasa Juric wrote: +</I>>>>>>><i> Hi, +</I>>>>>>><i> +</I>>>>>>><i> I have recently in my production system replaced mochiweb with cowboy. The server generally works fine, except for a bizarre behavior which I cannot quite explain, so I post here, hoping to get some pointers. +</I>>>>>>><i> +</I>>>>>>><i> After replacing mochiweb with cowboy, I noticed that in chromium (other major browsers work fine) often (but not always) a request lasts a little more than a minute. Further inspection in <A HREF="chrome://net-internals">chrome://net-internals</A> showed that browser tries to send a request, times out after 60 sec, retries and then succeeds immediately. The key point is that it doesn't happen always. First couple of requests work fine, then all of a sudden one doesn't work. At the same time requests from other browsers (including chrome) on the same machine work fine. +</I>>>>>>><i> +</I>>>>>>><i> If I revert to mochiweb, the problem disappears. Other than web server related code, everything else is the same: the rest of my code, the server setup etc... In addition, I return same responses and headers in both versions. +</I>>>>>>><i> +</I>>>>>>><i> After many attempts and failures, I might have worked around the issue. Namely, I included <<"connection">>, <<"close">> in all responses. After this change, it seems that long requests are not occurring. In any case, I can't reproduce it anymore, whereas before the change I could have reproduce it easily. +</I>>>>>>><i> +</I>>>>>>><i> However, I'm not sure if I have really resolved the issue, I'm also not happy with connection closes since it degrades performance. And finally, I'm not sure if I quite understand the problem. +</I>>>>>>><i> The only theory I have is that due to keep-alive, chromium holds the connection, while cowboy closes it (I read somewhere that hardcoded timeout is 5 seconds, right?). In this case it might happen that chromium sends a request to a non existing socket and then hangs for a minute, waiting for the response which never arrives. +</I>>>>>>><i> This might further be amplified by the fact that in production, between browser and cowboy, there is a proxy/load balancer, so maybe load balancer still holds the connection despite the fact that server had closed it. +</I>>>>>>><i> +</I>>>>>>><i> This is the only theory I currently have, and I would like to hear if you guys have some other idea or any kind of helpful pointer? +</I>>>>>><i> +</I>>>>>><i> Haven't seen this happen on plain Cowboy. The proxy might be the culprit. See if you can reproduce without the proxy. +</I>>>>>><i> +</I>>>>>><i> -- +</I>>>>>><i> Loïc Hoguin +</I>>>>>><i> Erlang Cowboy +</I>>>>>><i> Nine Nines +</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> Erlang Cowboy +</I>>>><i> Nine Nines +</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> Erlang Cowboy +</I>><i> Nine Nines +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000094.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000096.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#95">[ date ]</a> + <a href="thread.html#95">[ thread ]</a> + <a href="subject.html#95">[ subject ]</a> + <a href="author.html#95">[ 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/_build/static/archives/extend/2013-April/000096.html b/_build/static/archives/extend/2013-April/000096.html new file mode 100644 index 00000000..9e31920e --- /dev/null +++ b/_build/static/archives/extend/2013-April/000096.html @@ -0,0 +1,149 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy and chromium + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C51658026.2090805%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="000095.html"> + <LINK REL="Next" HREF="000097.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy and chromium</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3C51658026.2090805%40ninenines.eu%3E" + TITLE="[99s-extend] cowboy and chromium">essen at ninenines.eu + </A><BR> + <I>Wed Apr 10 17:07:18 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000095.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000097.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#96">[ date ]</a> + <a href="thread.html#96">[ thread ]</a> + <a href="subject.html#96">[ subject ]</a> + <a href="author.html#96">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>It's running from the moment Cowboy starts expecting a new request up to +the moment it got the request in full (excluding the body), then it's +reset for the next request. + +On 04/10/2013 05:05 PM, Sasa Juric wrote: +><i> Ok, just to make sure I understand: +</I>><i> When I serve a request, and the connection is not closed due to keep-alive, will this timeout also apply? +</I>><i> +</I>><i> +</I>><i> On Apr 10, 2013, at 5:01 PM, Loïc Hoguin wrote: +</I>><i> +</I>>><i> Means it's not a read timeout, but a timeout for the whole request up to and excluding the body (so an intentionally slow client will get disconnected at 5s). +</I>>><i> +</I>>><i> On 04/10/2013 04:56 PM, Sasa Juric wrote: +</I>>>><i> Thanks! +</I>>>><i> +</I>>>><i> I was looking at the option, but was confused by description which states: +</I>>>><i> Time in milliseconds a client has to send the full request line and headers. +</I>>>><i> +</I>>>><i> I'll give it a try and see how it works. +</I>>>><i> +</I>>>><i> Best regards, +</I>>>><i> Sasa +</I>>>><i> +</I>>>><i> On Apr 10, 2013, at 4:51 PM, Loïc Hoguin wrote: +</I>>>><i> +</I>>>>><i> 'timeout' protocol option, in milliseconds. +</I>>>>><i> +</I>>>>><i> On 04/10/2013 04:50 PM, Sasa Juric wrote: +</I>>>>>><i> I agree with you. In addition, I can't reproduce without the proxy, which confirms the suspicion. +</I>>>>>><i> +</I>>>>>><i> Looking at the code of mochiweb which I was using, the connection timeout is set to 5 minutes. +</I>>>>>><i> The other factor, which I can confirm is that when the server terminates the connection, the proxy doesn't forward this to the client. Hence, the client and proxy probably "think" that connection is still active, and try to reuse it, but this doesn't work until timeout. +</I>>>>>><i> Other browsers probably can gracefully handle this situation, but for some reason chromium is stuck to 60 seconds and after retry it presumably opens new connection and succeeds. +</I>>>>>><i> +</I>>>>>><i> Question: can I configure keep-alive timeout in Cowboy? +</I>>>>>><i> +</I>>>>>><i> +</I>>>>>><i> On Apr 10, 2013, at 4:41 PM, Loïc Hoguin wrote: +</I>>>>>><i> +</I>>>>>>><i> On 04/10/2013 02:00 PM, Sasa Juric wrote: +</I>>>>>>>><i> Hi, +</I>>>>>>>><i> +</I>>>>>>>><i> I have recently in my production system replaced mochiweb with cowboy. The server generally works fine, except for a bizarre behavior which I cannot quite explain, so I post here, hoping to get some pointers. +</I>>>>>>>><i> +</I>>>>>>>><i> After replacing mochiweb with cowboy, I noticed that in chromium (other major browsers work fine) often (but not always) a request lasts a little more than a minute. Further inspection in <A HREF="chrome://net-internals">chrome://net-internals</A> showed that browser tries to send a request, times out after 60 sec, retries and then succeeds immediately. The key point is that it doesn't happen always. First couple of requests work fine, then all of a sudden one doesn't work. At the same time requests from other browsers (including chrome) on the same machine work fine. +</I>>>>>>>><i> +</I>>>>>>>><i> If I revert to mochiweb, the problem disappears. Other than web server related code, everything else is the same: the rest of my code, the server setup etc... In addition, I return same responses and headers in both versions. +</I>>>>>>>><i> +</I>>>>>>>><i> After many attempts and failures, I might have worked around the issue. Namely, I included <<"connection">>, <<"close">> in all responses. After this change, it seems that long requests are not occurring. In any case, I can't reproduce it anymore, whereas before the change I could have reproduce it easily. +</I>>>>>>>><i> +</I>>>>>>>><i> However, I'm not sure if I have really resolved the issue, I'm also not happy with connection closes since it degrades performance. And finally, I'm not sure if I quite understand the problem. +</I>>>>>>>><i> The only theory I have is that due to keep-alive, chromium holds the connection, while cowboy closes it (I read somewhere that hardcoded timeout is 5 seconds, right?). In this case it might happen that chromium sends a request to a non existing socket and then hangs for a minute, waiting for the response which never arrives. +</I>>>>>>>><i> This might further be amplified by the fact that in production, between browser and cowboy, there is a proxy/load balancer, so maybe load balancer still holds the connection despite the fact that server had closed it. +</I>>>>>>>><i> +</I>>>>>>>><i> This is the only theory I currently have, and I would like to hear if you guys have some other idea or any kind of helpful pointer? +</I>>>>>>><i> +</I>>>>>>><i> Haven't seen this happen on plain Cowboy. The proxy might be the culprit. See if you can reproduce without the proxy. +</I>>>>>>><i> +</I>>>>>>><i> -- +</I>>>>>>><i> Loïc Hoguin +</I>>>>>>><i> Erlang Cowboy +</I>>>>>>><i> Nine Nines +</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> Erlang Cowboy +</I>>>>><i> Nine Nines +</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> Erlang Cowboy +</I>>><i> Nine Nines +</I>>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I> + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000095.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000097.html">[99s-extend] cowboy and chromium +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#96">[ date ]</a> + <a href="thread.html#96">[ thread ]</a> + <a href="subject.html#96">[ subject ]</a> + <a href="author.html#96">[ 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/_build/static/archives/extend/2013-April/000097.html b/_build/static/archives/extend/2013-April/000097.html new file mode 100644 index 00000000..0fce37e1 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000097.html @@ -0,0 +1,152 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy and chromium + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3CB51E1290-B953-4A81-9B1F-BA9229E65AF1%40gmail.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="000096.html"> + <LINK REL="Next" HREF="000098.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy and chromium</H1> + <B>Sasa Juric</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20and%20chromium&In-Reply-To=%3CB51E1290-B953-4A81-9B1F-BA9229E65AF1%40gmail.com%3E" + TITLE="[99s-extend] cowboy and chromium">sasa.juric at gmail.com + </A><BR> + <I>Wed Apr 10 17:11:57 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000096.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000098.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#97">[ date ]</a> + <a href="thread.html#97">[ thread ]</a> + <a href="subject.html#97">[ subject ]</a> + <a href="author.html#97">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thanks! + +On Apr 10, 2013, at 5:07 PM, Loïc Hoguin wrote: + +><i> It's running from the moment Cowboy starts expecting a new request up to the moment it got the request in full (excluding the body), then it's reset for the next request. +</I>><i> +</I>><i> On 04/10/2013 05:05 PM, Sasa Juric wrote: +</I>>><i> Ok, just to make sure I understand: +</I>>><i> When I serve a request, and the connection is not closed due to keep-alive, will this timeout also apply? +</I>>><i> +</I>>><i> +</I>>><i> On Apr 10, 2013, at 5:01 PM, Loïc Hoguin wrote: +</I>>><i> +</I>>>><i> Means it's not a read timeout, but a timeout for the whole request up to and excluding the body (so an intentionally slow client will get disconnected at 5s). +</I>>>><i> +</I>>>><i> On 04/10/2013 04:56 PM, Sasa Juric wrote: +</I>>>>><i> Thanks! +</I>>>>><i> +</I>>>>><i> I was looking at the option, but was confused by description which states: +</I>>>>><i> Time in milliseconds a client has to send the full request line and headers. +</I>>>>><i> +</I>>>>><i> I'll give it a try and see how it works. +</I>>>>><i> +</I>>>>><i> Best regards, +</I>>>>><i> Sasa +</I>>>>><i> +</I>>>>><i> On Apr 10, 2013, at 4:51 PM, Loïc Hoguin wrote: +</I>>>>><i> +</I>>>>>><i> 'timeout' protocol option, in milliseconds. +</I>>>>>><i> +</I>>>>>><i> On 04/10/2013 04:50 PM, Sasa Juric wrote: +</I>>>>>>><i> I agree with you. In addition, I can't reproduce without the proxy, which confirms the suspicion. +</I>>>>>>><i> +</I>>>>>>><i> Looking at the code of mochiweb which I was using, the connection timeout is set to 5 minutes. +</I>>>>>>><i> The other factor, which I can confirm is that when the server terminates the connection, the proxy doesn't forward this to the client. Hence, the client and proxy probably "think" that connection is still active, and try to reuse it, but this doesn't work until timeout. +</I>>>>>>><i> Other browsers probably can gracefully handle this situation, but for some reason chromium is stuck to 60 seconds and after retry it presumably opens new connection and succeeds. +</I>>>>>>><i> +</I>>>>>>><i> Question: can I configure keep-alive timeout in Cowboy? +</I>>>>>>><i> +</I>>>>>>><i> +</I>>>>>>><i> On Apr 10, 2013, at 4:41 PM, Loïc Hoguin wrote: +</I>>>>>>><i> +</I>>>>>>>><i> On 04/10/2013 02:00 PM, Sasa Juric wrote: +</I>>>>>>>>><i> Hi, +</I>>>>>>>>><i> +</I>>>>>>>>><i> I have recently in my production system replaced mochiweb with cowboy. The server generally works fine, except for a bizarre behavior which I cannot quite explain, so I post here, hoping to get some pointers. +</I>>>>>>>>><i> +</I>>>>>>>>><i> After replacing mochiweb with cowboy, I noticed that in chromium (other major browsers work fine) often (but not always) a request lasts a little more than a minute. Further inspection in <A HREF="chrome://net-internals">chrome://net-internals</A> showed that browser tries to send a request, times out after 60 sec, retries and then succeeds immediately. The key point is that it doesn't happen always. First couple of requests work fine, then all of a sudden one doesn't work. At the same time requests from other browsers (including chrome) on the same machine work fine. +</I>>>>>>>>><i> +</I>>>>>>>>><i> If I revert to mochiweb, the problem disappears. Other than web server related code, everything else is the same: the rest of my code, the server setup etc... In addition, I return same responses and headers in both versions. +</I>>>>>>>>><i> +</I>>>>>>>>><i> After many attempts and failures, I might have worked around the issue. Namely, I included <<"connection">>, <<"close">> in all responses. After this change, it seems that long requests are not occurring. In any case, I can't reproduce it anymore, whereas before the change I could have reproduce it easily. +</I>>>>>>>>><i> +</I>>>>>>>>><i> However, I'm not sure if I have really resolved the issue, I'm also not happy with connection closes since it degrades performance. And finally, I'm not sure if I quite understand the problem. +</I>>>>>>>>><i> The only theory I have is that due to keep-alive, chromium holds the connection, while cowboy closes it (I read somewhere that hardcoded timeout is 5 seconds, right?). In this case it might happen that chromium sends a request to a non existing socket and then hangs for a minute, waiting for the response which never arrives. +</I>>>>>>>>><i> This might further be amplified by the fact that in production, between browser and cowboy, there is a proxy/load balancer, so maybe load balancer still holds the connection despite the fact that server had closed it. +</I>>>>>>>>><i> +</I>>>>>>>>><i> This is the only theory I currently have, and I would like to hear if you guys have some other idea or any kind of helpful pointer? +</I>>>>>>>><i> +</I>>>>>>>><i> Haven't seen this happen on plain Cowboy. The proxy might be the culprit. See if you can reproduce without the proxy. +</I>>>>>>>><i> +</I>>>>>>>><i> -- +</I>>>>>>>><i> Loïc Hoguin +</I>>>>>>>><i> Erlang Cowboy +</I>>>>>>>><i> Nine Nines +</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> Erlang Cowboy +</I>>>>>><i> Nine Nines +</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> Erlang Cowboy +</I>>>><i> Nine Nines +</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> Erlang Cowboy +</I>><i> Nine Nines +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000096.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000098.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#97">[ date ]</a> + <a href="thread.html#97">[ thread ]</a> + <a href="subject.html#97">[ subject ]</a> + <a href="author.html#97">[ 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/_build/static/archives/extend/2013-April/000098.html b/_build/static/archives/extend/2013-April/000098.html new file mode 100644 index 00000000..ee3ce9ba --- /dev/null +++ b/_build/static/archives/extend/2013-April/000098.html @@ -0,0 +1,68 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Distributed model? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3CADCAD0B2-A081-44CA-82F5-B544F355956F%40gmail.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="000097.html"> + <LINK REL="Next" HREF="000099.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Distributed model?</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3CADCAD0B2-A081-44CA-82F5-B544F355956F%40gmail.com%3E" + TITLE="[99s-extend] Distributed model?">lee.sylvester at gmail.com + </A><BR> + <I>Thu Apr 11 07:51:12 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000097.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000099.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#98">[ date ]</a> + <a href="thread.html#98">[ thread ]</a> + <a href="subject.html#98">[ subject ]</a> + <a href="author.html#98">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi guys, + +So, I have my Cowboy / Bullet server working nicely, now, with much thanks to members on this list. I'm now looking at the best means of clustering this app. I want to set this up so that, should the connection count get very high (which it will), then I should only have to throw more machines at this problem and it'll all go away. + +I've got most of the logic working for this, but what I'm worried about is sending a lot of content over the erlang inter-node connection. I've heard hogging this line can be both a bottleneck and can potentially interrupt the heartbeat between nodes. With this in mind, should I look at adding a ZMQ layer or some such to facilitate this? What is the general solution to high traffic between nodes? + +Thanks, +Lee +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000097.html">[99s-extend] cowboy and chromium +</A></li> + <LI>Next message: <A HREF="000099.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#98">[ date ]</a> + <a href="thread.html#98">[ thread ]</a> + <a href="subject.html#98">[ subject ]</a> + <a href="author.html#98">[ 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/_build/static/archives/extend/2013-April/000099.html b/_build/static/archives/extend/2013-April/000099.html new file mode 100644 index 00000000..3bab2cbe --- /dev/null +++ b/_build/static/archives/extend/2013-April/000099.html @@ -0,0 +1,80 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Distributed model? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3CCAKD1GY6z-Au5C-AsOus2ieOEtGymgigYp_SzGhrt%2BGgaXNFd%3DQ%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="000098.html"> + <LINK REL="Next" HREF="000100.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Distributed model?</H1> + <B>Jeremy Ong</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3CCAKD1GY6z-Au5C-AsOus2ieOEtGymgigYp_SzGhrt%2BGgaXNFd%3DQ%40mail.gmail.com%3E" + TITLE="[99s-extend] Distributed model?">jeremy at quarkgames.com + </A><BR> + <I>Thu Apr 11 08:29:16 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000098.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000100.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#99">[ date ]</a> + <a href="thread.html#99">[ thread ]</a> + <a href="subject.html#99">[ subject ]</a> + <a href="author.html#99">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Make all the machines identically and add an haproxy (or equivalent) +machine to load balance between all of them. Haproxy can handle many +many requests. Keep in mind that with tcp, the load balancer is just +accepting the socket but then the client communicates with the actual +application server directly afterwards. + +On Wed, Apr 10, 2013 at 10:51 PM, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +><i> Hi guys, +</I>><i> +</I>><i> So, I have my Cowboy / Bullet server working nicely, now, with much thanks to members on this list. I'm now looking at the best means of clustering this app. I want to set this up so that, should the connection count get very high (which it will), then I should only have to throw more machines at this problem and it'll all go away. +</I>><i> +</I>><i> I've got most of the logic working for this, but what I'm worried about is sending a lot of content over the erlang inter-node connection. I've heard hogging this line can be both a bottleneck and can potentially interrupt the heartbeat between nodes. With this in mind, should I look at adding a ZMQ layer or some such to facilitate this? What is the general solution to high traffic between nodes? +</I>><i> +</I>><i> Thanks, +</I>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000098.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000100.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#99">[ date ]</a> + <a href="thread.html#99">[ thread ]</a> + <a href="subject.html#99">[ subject ]</a> + <a href="author.html#99">[ 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/_build/static/archives/extend/2013-April/000100.html b/_build/static/archives/extend/2013-April/000100.html new file mode 100644 index 00000000..1efa066a --- /dev/null +++ b/_build/static/archives/extend/2013-April/000100.html @@ -0,0 +1,89 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Distributed model? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3C8456939C-6A11-4A18-BD8A-DF378644DACB%40gmail.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="000099.html"> + <LINK REL="Next" HREF="000101.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Distributed model?</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3C8456939C-6A11-4A18-BD8A-DF378644DACB%40gmail.com%3E" + TITLE="[99s-extend] Distributed model?">lee.sylvester at gmail.com + </A><BR> + <I>Thu Apr 11 08:49:18 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000099.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000101.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#100">[ date ]</a> + <a href="thread.html#100">[ thread ]</a> + <a href="subject.html#100">[ subject ]</a> + <a href="author.html#100">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thanks Jeremy, but what about inter-node communication? If I have a user on node A sending a message to 10k users located on 10 other nodes, what is the best way to handle that? Especially if this user is sending several messages and expecting replies. Should I use the standard Erlang inter-process messaging or should I implement an MQ on top to handle this? + +Thanks, +Lee + + +On 11 Apr 2013, at 07:29, Jeremy Ong <<A HREF="https://lists.ninenines.eu/listinfo/extend">jeremy at quarkgames.com</A>> wrote: + +><i> Make all the machines identically and add an haproxy (or equivalent) +</I>><i> machine to load balance between all of them. Haproxy can handle many +</I>><i> many requests. Keep in mind that with tcp, the load balancer is just +</I>><i> accepting the socket but then the client communicates with the actual +</I>><i> application server directly afterwards. +</I>><i> +</I>><i> On Wed, Apr 10, 2013 at 10:51 PM, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>>><i> Hi guys, +</I>>><i> +</I>>><i> So, I have my Cowboy / Bullet server working nicely, now, with much thanks to members on this list. I'm now looking at the best means of clustering this app. I want to set this up so that, should the connection count get very high (which it will), then I should only have to throw more machines at this problem and it'll all go away. +</I>>><i> +</I>>><i> I've got most of the logic working for this, but what I'm worried about is sending a lot of content over the erlang inter-node connection. I've heard hogging this line can be both a bottleneck and can potentially interrupt the heartbeat between nodes. With this in mind, should I look at adding a ZMQ layer or some such to facilitate this? What is the general solution to high traffic between nodes? +</I>>><i> +</I>>><i> Thanks, +</I>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000099.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000101.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#100">[ date ]</a> + <a href="thread.html#100">[ thread ]</a> + <a href="subject.html#100">[ subject ]</a> + <a href="author.html#100">[ 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/_build/static/archives/extend/2013-April/000101.html b/_build/static/archives/extend/2013-April/000101.html new file mode 100644 index 00000000..9202db3c --- /dev/null +++ b/_build/static/archives/extend/2013-April/000101.html @@ -0,0 +1,102 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Distributed model? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3CCAKD1GY4xtZWXvfqstapnpLskbn3DFPPGDO9yHTLHDmTP%2BozR7A%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="000100.html"> + <LINK REL="Next" HREF="000102.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Distributed model?</H1> + <B>Jeremy Ong</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3CCAKD1GY4xtZWXvfqstapnpLskbn3DFPPGDO9yHTLHDmTP%2BozR7A%40mail.gmail.com%3E" + TITLE="[99s-extend] Distributed model?">jeremy at quarkgames.com + </A><BR> + <I>Thu Apr 11 09:04:04 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000100.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000102.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#101">[ date ]</a> + <a href="thread.html#101">[ thread ]</a> + <a href="subject.html#101">[ subject ]</a> + <a href="author.html#101">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>I see. I assume this is for a chat server of some sort? + +You don't want the user process sending all these messages because the +user process wouldn't be able to do anything useful (like receive +messages) in the meantime. + +Better is to implement a pubsub process for each channel of +communication (i.e. one process per room) or rely on Redis pubsub or +something if speed is extremely important. + +There is no way to get around the O(N) complexity of broadcasting. + +On Wed, Apr 10, 2013 at 11:49 PM, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +><i> Thanks Jeremy, but what about inter-node communication? If I have a user on node A sending a message to 10k users located on 10 other nodes, what is the best way to handle that? Especially if this user is sending several messages and expecting replies. Should I use the standard Erlang inter-process messaging or should I implement an MQ on top to handle this? +</I>><i> +</I>><i> Thanks, +</I>><i> Lee +</I>><i> +</I>><i> +</I>><i> On 11 Apr 2013, at 07:29, Jeremy Ong <<A HREF="https://lists.ninenines.eu/listinfo/extend">jeremy at quarkgames.com</A>> wrote: +</I>><i> +</I>>><i> Make all the machines identically and add an haproxy (or equivalent) +</I>>><i> machine to load balance between all of them. Haproxy can handle many +</I>>><i> many requests. Keep in mind that with tcp, the load balancer is just +</I>>><i> accepting the socket but then the client communicates with the actual +</I>>><i> application server directly afterwards. +</I>>><i> +</I>>><i> On Wed, Apr 10, 2013 at 10:51 PM, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>>>><i> Hi guys, +</I>>>><i> +</I>>>><i> So, I have my Cowboy / Bullet server working nicely, now, with much thanks to members on this list. I'm now looking at the best means of clustering this app. I want to set this up so that, should the connection count get very high (which it will), then I should only have to throw more machines at this problem and it'll all go away. +</I>>>><i> +</I>>>><i> I've got most of the logic working for this, but what I'm worried about is sending a lot of content over the erlang inter-node connection. I've heard hogging this line can be both a bottleneck and can potentially interrupt the heartbeat between nodes. With this in mind, should I look at adding a ZMQ layer or some such to facilitate this? What is the general solution to high traffic between nodes? +</I>>>><i> +</I>>>><i> Thanks, +</I>>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000100.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000102.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#101">[ date ]</a> + <a href="thread.html#101">[ thread ]</a> + <a href="subject.html#101">[ subject ]</a> + <a href="author.html#101">[ 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/_build/static/archives/extend/2013-April/000102.html b/_build/static/archives/extend/2013-April/000102.html new file mode 100644 index 00000000..c9d55344 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000102.html @@ -0,0 +1,112 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Distributed model? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3CD7BCE9BB-C9D2-4423-92EC-14D4DC841D6F%40gmail.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="000101.html"> + <LINK REL="Next" HREF="000103.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Distributed model?</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3CD7BCE9BB-C9D2-4423-92EC-14D4DC841D6F%40gmail.com%3E" + TITLE="[99s-extend] Distributed model?">lee.sylvester at gmail.com + </A><BR> + <I>Thu Apr 11 14:55:29 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000101.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000103.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#102">[ date ]</a> + <a href="thread.html#102">[ thread ]</a> + <a href="subject.html#102">[ subject ]</a> + <a href="author.html#102">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thank you, Jeremy, that's good advice. It's not so much a chat platform, but I guess it would resemble one in architecture. The part I'm concerned about, though, is should I be avoiding the internal Erlang messaging between connections (over many nodes) for heavy messaging? + +Thanks, +Lee + + + +On 11 Apr 2013, at 08:04, Jeremy Ong <<A HREF="https://lists.ninenines.eu/listinfo/extend">jeremy at quarkgames.com</A>> wrote: + +><i> I see. I assume this is for a chat server of some sort? +</I>><i> +</I>><i> You don't want the user process sending all these messages because the +</I>><i> user process wouldn't be able to do anything useful (like receive +</I>><i> messages) in the meantime. +</I>><i> +</I>><i> Better is to implement a pubsub process for each channel of +</I>><i> communication (i.e. one process per room) or rely on Redis pubsub or +</I>><i> something if speed is extremely important. +</I>><i> +</I>><i> There is no way to get around the O(N) complexity of broadcasting. +</I>><i> +</I>><i> On Wed, Apr 10, 2013 at 11:49 PM, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>>><i> Thanks Jeremy, but what about inter-node communication? If I have a user on node A sending a message to 10k users located on 10 other nodes, what is the best way to handle that? Especially if this user is sending several messages and expecting replies. Should I use the standard Erlang inter-process messaging or should I implement an MQ on top to handle this? +</I>>><i> +</I>>><i> Thanks, +</I>>><i> Lee +</I>>><i> +</I>>><i> +</I>>><i> On 11 Apr 2013, at 07:29, Jeremy Ong <<A HREF="https://lists.ninenines.eu/listinfo/extend">jeremy at quarkgames.com</A>> wrote: +</I>>><i> +</I>>>><i> Make all the machines identically and add an haproxy (or equivalent) +</I>>>><i> machine to load balance between all of them. Haproxy can handle many +</I>>>><i> many requests. Keep in mind that with tcp, the load balancer is just +</I>>>><i> accepting the socket but then the client communicates with the actual +</I>>>><i> application server directly afterwards. +</I>>>><i> +</I>>>><i> On Wed, Apr 10, 2013 at 10:51 PM, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>>>>><i> Hi guys, +</I>>>>><i> +</I>>>>><i> So, I have my Cowboy / Bullet server working nicely, now, with much thanks to members on this list. I'm now looking at the best means of clustering this app. I want to set this up so that, should the connection count get very high (which it will), then I should only have to throw more machines at this problem and it'll all go away. +</I>>>>><i> +</I>>>>><i> I've got most of the logic working for this, but what I'm worried about is sending a lot of content over the erlang inter-node connection. I've heard hogging this line can be both a bottleneck and can potentially interrupt the heartbeat between nodes. With this in mind, should I look at adding a ZMQ layer or some such to facilitate this? What is the general solution to high traffic between nodes? +</I>>>>><i> +</I>>>>><i> Thanks, +</I>>>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>><i> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000101.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000103.html">[99s-extend] Distributed model? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#102">[ date ]</a> + <a href="thread.html#102">[ thread ]</a> + <a href="subject.html#102">[ subject ]</a> + <a href="author.html#102">[ 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/_build/static/archives/extend/2013-April/000103.html b/_build/static/archives/extend/2013-April/000103.html new file mode 100644 index 00000000..28c7c536 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000103.html @@ -0,0 +1,122 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Distributed model? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3C4011ABA6-BD55-4DEB-BE8F-2E20F2376A25%40gmail.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="000102.html"> + <LINK REL="Next" HREF="000104.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Distributed model?</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3C4011ABA6-BD55-4DEB-BE8F-2E20F2376A25%40gmail.com%3E" + TITLE="[99s-extend] Distributed model?">lee.sylvester at gmail.com + </A><BR> + <I>Thu Apr 11 17:46:35 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000102.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000104.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#103">[ date ]</a> + <a href="thread.html#103">[ thread ]</a> + <a href="subject.html#103">[ subject ]</a> + <a href="author.html#103">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Okay, so I've figured it out. I will need to have a separate messaging layer. Does anyone know of a messaging layer that can be used when all you know is the PID to send to? + +Thanks, +Lee + + + +On 11 Apr 2013, at 13:55, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: + +><i> Thank you, Jeremy, that's good advice. It's not so much a chat platform, but I guess it would resemble one in architecture. The part I'm concerned about, though, is should I be avoiding the internal Erlang messaging between connections (over many nodes) for heavy messaging? +</I>><i> +</I>><i> Thanks, +</I>><i> Lee +</I>><i> +</I>><i> +</I>><i> +</I>><i> On 11 Apr 2013, at 08:04, Jeremy Ong <<A HREF="https://lists.ninenines.eu/listinfo/extend">jeremy at quarkgames.com</A>> wrote: +</I>><i> +</I>>><i> I see. I assume this is for a chat server of some sort? +</I>>><i> +</I>>><i> You don't want the user process sending all these messages because the +</I>>><i> user process wouldn't be able to do anything useful (like receive +</I>>><i> messages) in the meantime. +</I>>><i> +</I>>><i> Better is to implement a pubsub process for each channel of +</I>>><i> communication (i.e. one process per room) or rely on Redis pubsub or +</I>>><i> something if speed is extremely important. +</I>>><i> +</I>>><i> There is no way to get around the O(N) complexity of broadcasting. +</I>>><i> +</I>>><i> On Wed, Apr 10, 2013 at 11:49 PM, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>>>><i> Thanks Jeremy, but what about inter-node communication? If I have a user on node A sending a message to 10k users located on 10 other nodes, what is the best way to handle that? Especially if this user is sending several messages and expecting replies. Should I use the standard Erlang inter-process messaging or should I implement an MQ on top to handle this? +</I>>>><i> +</I>>>><i> Thanks, +</I>>>><i> Lee +</I>>>><i> +</I>>>><i> +</I>>>><i> On 11 Apr 2013, at 07:29, Jeremy Ong <<A HREF="https://lists.ninenines.eu/listinfo/extend">jeremy at quarkgames.com</A>> wrote: +</I>>>><i> +</I>>>>><i> Make all the machines identically and add an haproxy (or equivalent) +</I>>>>><i> machine to load balance between all of them. Haproxy can handle many +</I>>>>><i> many requests. Keep in mind that with tcp, the load balancer is just +</I>>>>><i> accepting the socket but then the client communicates with the actual +</I>>>>><i> application server directly afterwards. +</I>>>>><i> +</I>>>>><i> On Wed, Apr 10, 2013 at 10:51 PM, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>>>>>><i> Hi guys, +</I>>>>>><i> +</I>>>>>><i> So, I have my Cowboy / Bullet server working nicely, now, with much thanks to members on this list. I'm now looking at the best means of clustering this app. I want to set this up so that, should the connection count get very high (which it will), then I should only have to throw more machines at this problem and it'll all go away. +</I>>>>>><i> +</I>>>>>><i> I've got most of the logic working for this, but what I'm worried about is sending a lot of content over the erlang inter-node connection. I've heard hogging this line can be both a bottleneck and can potentially interrupt the heartbeat between nodes. With this in mind, should I look at adding a ZMQ layer or some such to facilitate this? What is the general solution to high traffic between nodes? +</I>>>>>><i> +</I>>>>>><i> Thanks, +</I>>>>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>>><i> +</I>><i> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000102.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000104.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#103">[ date ]</a> + <a href="thread.html#103">[ thread ]</a> + <a href="subject.html#103">[ subject ]</a> + <a href="author.html#103">[ 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/_build/static/archives/extend/2013-April/000104.html b/_build/static/archives/extend/2013-April/000104.html new file mode 100644 index 00000000..692c6f64 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000104.html @@ -0,0 +1,127 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] populating #http_req for unit testing + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20populating%20%23http_req%20for%20unit%20testing&In-Reply-To=%3CCD8CBFE1.A141%25kevin.brown%40turner.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="000103.html"> + <LINK REL="Next" HREF="000105.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] populating #http_req for unit testing</H1> + <B>Brown, Kevin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20populating%20%23http_req%20for%20unit%20testing&In-Reply-To=%3CCD8CBFE1.A141%25kevin.brown%40turner.com%3E" + TITLE="[99s-extend] populating #http_req for unit testing">Kevin.Brown at turner.com + </A><BR> + <I>Fri Apr 12 01:37:18 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000103.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000105.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#104">[ date ]</a> + <a href="thread.html#104">[ thread ]</a> + <a href="subject.html#104">[ subject ]</a> + <a href="author.html#104">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> +Cowfolk, + +I am doing something like this to create an #http_req suitable for unit +testing my resource callbacks: + +-define (HTTP_REQ_ENCODERS_PORT_8000, #http_req{host= <<"www.foo.com">> , +port=8000, path= <<"/encoders">>,transport=ranch_tcp, qs= <<>>, fragment= +<<>> }). + +Notice that I needed to set the transport to a Cowboy specific atom +because I wanted to get cowboy_req:host_url and cowboy_req:path to work +properly. + +I'm sure there is a method that Cowboy uses internally to populate an +#http_req from a URL that I could use for testing. What might that be? +How else should I be populating this record. + +Cheers, + +-kb + + + + + + +On 4/11/13 7:07 PM, "<A HREF="https://lists.ninenines.eu/listinfo/extend">extend-request at lists.ninenines.eu</A>" +<<A HREF="https://lists.ninenines.eu/listinfo/extend">extend-request at lists.ninenines.eu</A>> wrote: + +><i>Welcome to the <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A> mailing list! +</I>><i> +</I>><i>To post to this list, send your message to: +</I>><i> +</I>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">extend at lists.ninenines.eu</A> +</I>><i> +</I>><i>General information about the mailing list is at: +</I>><i> +</I>><i> <A HREF="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I>><i>If you ever want to unsubscribe or change your options (eg, switch to +</I>><i>or from digest mode, change your password, etc.), visit your +</I>><i>subscription page at: +</I>><i> +</I>><i> <A HREF="http://lists.ninenines.eu:81/options/extend/kevin.brown%40turner.com">http://lists.ninenines.eu:81/options/extend/kevin.brown%40turner.com</A> +</I>><i> +</I>><i>You can also make such adjustments via email by sending a message to: +</I>><i> +</I>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend-request at lists.ninenines.eu</A> +</I>><i> +</I>><i>with the word `help' in the subject or body (don't include the +</I>><i>quotes), and you will get back a message with instructions. +</I>><i> +</I>><i>You must know your password to change your options (including changing +</I>><i>the password, itself) or to unsubscribe without confirmation. It is: +</I>><i> +</I>><i> doofus1 +</I>><i> +</I>><i>Normally, Mailman will remind you of your lists.ninenines.eu mailing +</I>><i>list passwords once every month, although you can disable this if you +</I>><i>prefer. This reminder will also include instructions on how to +</I>><i>unsubscribe or change your account options. There is also a button on +</I>><i>your options page that will email your current password to you. +</I>><i> +</I> + + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000103.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000105.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#104">[ date ]</a> + <a href="thread.html#104">[ thread ]</a> + <a href="subject.html#104">[ subject ]</a> + <a href="author.html#104">[ 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/_build/static/archives/extend/2013-April/000105.html b/_build/static/archives/extend/2013-April/000105.html new file mode 100644 index 00000000..001e12f6 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000105.html @@ -0,0 +1,143 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] populating #http_req for unit testing + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20populating%20%23http_req%20for%20unit%20testing&In-Reply-To=%3C5167503E.5070204%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="000104.html"> + <LINK REL="Next" HREF="000106.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] populating #http_req for unit testing</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20populating%20%23http_req%20for%20unit%20testing&In-Reply-To=%3C5167503E.5070204%40ninenines.eu%3E" + TITLE="[99s-extend] populating #http_req for unit testing">essen at ninenines.eu + </A><BR> + <I>Fri Apr 12 02:07:26 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000104.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI>Next message: <A HREF="000106.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#105">[ date ]</a> + <a href="thread.html#105">[ thread ]</a> + <a href="subject.html#105">[ subject ]</a> + <a href="author.html#105">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>There's a few undocumented functions in cowboy_req, like new, set and +get, used by Cowboy internally. + +On 04/12/2013 01:37 AM, Brown, Kevin wrote: +><i> +</I>><i> Cowfolk, +</I>><i> +</I>><i> I am doing something like this to create an #http_req suitable for unit +</I>><i> testing my resource callbacks: +</I>><i> +</I>><i> -define (HTTP_REQ_ENCODERS_PORT_8000, #http_req{host= <<"www.foo.com">> , +</I>><i> port=8000, path= <<"/encoders">>,transport=ranch_tcp, qs= <<>>, fragment= +</I>><i> <<>> }). +</I>><i> +</I>><i> Notice that I needed to set the transport to a Cowboy specific atom +</I>><i> because I wanted to get cowboy_req:host_url and cowboy_req:path to work +</I>><i> properly. +</I>><i> +</I>><i> I'm sure there is a method that Cowboy uses internally to populate an +</I>><i> #http_req from a URL that I could use for testing. What might that be? +</I>><i> How else should I be populating this record. +</I>><i> +</I>><i> Cheers, +</I>><i> +</I>><i> -kb +</I>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i> On 4/11/13 7:07 PM, "<A HREF="https://lists.ninenines.eu/listinfo/extend">extend-request at lists.ninenines.eu</A>" +</I>><i> <<A HREF="https://lists.ninenines.eu/listinfo/extend">extend-request at lists.ninenines.eu</A>> wrote: +</I>><i> +</I>>><i> Welcome to the <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A> mailing list! +</I>>><i> +</I>>><i> To post to this list, send your message to: +</I>>><i> +</I>>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">extend at lists.ninenines.eu</A> +</I>>><i> +</I>>><i> General information about the mailing list is at: +</I>>><i> +</I>>><i> <A HREF="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>><i> +</I>>><i> If you ever want to unsubscribe or change your options (eg, switch to +</I>>><i> or from digest mode, change your password, etc.), visit your +</I>>><i> subscription page at: +</I>>><i> +</I>>><i> <A HREF="http://lists.ninenines.eu:81/options/extend/kevin.brown%40turner.com">http://lists.ninenines.eu:81/options/extend/kevin.brown%40turner.com</A> +</I>>><i> +</I>>><i> You can also make such adjustments via email by sending a message to: +</I>>><i> +</I>>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend-request at lists.ninenines.eu</A> +</I>>><i> +</I>>><i> with the word `help' in the subject or body (don't include the +</I>>><i> quotes), and you will get back a message with instructions. +</I>>><i> +</I>>><i> You must know your password to change your options (including changing +</I>>><i> the password, itself) or to unsubscribe without confirmation. It is: +</I>>><i> +</I>>><i> doofus1 +</I>>><i> +</I>>><i> Normally, Mailman will remind you of your lists.ninenines.eu mailing +</I>>><i> list passwords once every month, although you can disable this if you +</I>>><i> prefer. This reminder will also include instructions on how to +</I>>><i> unsubscribe or change your account options. There is also a button on +</I>>><i> your options page that will email your current password to you. +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I> + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000104.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI>Next message: <A HREF="000106.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#105">[ date ]</a> + <a href="thread.html#105">[ thread ]</a> + <a href="subject.html#105">[ subject ]</a> + <a href="author.html#105">[ 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/_build/static/archives/extend/2013-April/000106.html b/_build/static/archives/extend/2013-April/000106.html new file mode 100644 index 00000000..fc45bb84 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000106.html @@ -0,0 +1,152 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] populating #http_req for unit testing + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20populating%20%23http_req%20for%20unit%20testing&In-Reply-To=%3CCD8CCDCD.A1C9%25kevin.brown%40turner.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="000105.html"> + <LINK REL="Next" HREF="000107.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] populating #http_req for unit testing</H1> + <B>Brown, Kevin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20populating%20%23http_req%20for%20unit%20testing&In-Reply-To=%3CCD8CCDCD.A1C9%25kevin.brown%40turner.com%3E" + TITLE="[99s-extend] populating #http_req for unit testing">Kevin.Brown at turner.com + </A><BR> + <I>Fri Apr 12 02:30:15 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000105.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI>Next message: <A HREF="000107.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#106">[ date ]</a> + <a href="thread.html#106">[ thread ]</a> + <a href="subject.html#106">[ subject ]</a> + <a href="author.html#106">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thanks. + +On 4/11/13 8:07 PM, "Loïc Hoguin" <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: + +><i>There's a few undocumented functions in cowboy_req, like new, set and +</I>><i>get, used by Cowboy internally. +</I>><i> +</I>><i>On 04/12/2013 01:37 AM, Brown, Kevin wrote: +</I>>><i> +</I>>><i> Cowfolk, +</I>>><i> +</I>>><i> I am doing something like this to create an #http_req suitable for unit +</I>>><i> testing my resource callbacks: +</I>>><i> +</I>>><i> -define (HTTP_REQ_ENCODERS_PORT_8000, #http_req{host= +</I>>><i><<"www.foo.com">> , +</I>>><i> port=8000, path= <<"/encoders">>,transport=ranch_tcp, qs= <<>>, +</I>>><i>fragment= +</I>>><i> <<>> }). +</I>>><i> +</I>>><i> Notice that I needed to set the transport to a Cowboy specific atom +</I>>><i> because I wanted to get cowboy_req:host_url and cowboy_req:path to work +</I>>><i> properly. +</I>>><i> +</I>>><i> I'm sure there is a method that Cowboy uses internally to populate an +</I>>><i> #http_req from a URL that I could use for testing. What might that be? +</I>>><i> How else should I be populating this record. +</I>>><i> +</I>>><i> Cheers, +</I>>><i> +</I>>><i> -kb +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> On 4/11/13 7:07 PM, "<A HREF="https://lists.ninenines.eu/listinfo/extend">extend-request at lists.ninenines.eu</A>" +</I>>><i> <<A HREF="https://lists.ninenines.eu/listinfo/extend">extend-request at lists.ninenines.eu</A>> wrote: +</I>>><i> +</I>>>><i> Welcome to the <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A> mailing list! +</I>>>><i> +</I>>>><i> To post to this list, send your message to: +</I>>>><i> +</I>>>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">extend at lists.ninenines.eu</A> +</I>>>><i> +</I>>>><i> General information about the mailing list is at: +</I>>>><i> +</I>>>><i> <A HREF="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>>><i> +</I>>>><i> If you ever want to unsubscribe or change your options (eg, switch to +</I>>>><i> or from digest mode, change your password, etc.), visit your +</I>>>><i> subscription page at: +</I>>>><i> +</I>>>><i> <A HREF="http://lists.ninenines.eu:81/options/extend/kevin.brown%40turner.com">http://lists.ninenines.eu:81/options/extend/kevin.brown%40turner.com</A> +</I>>>><i> +</I>>>><i> You can also make such adjustments via email by sending a message to: +</I>>>><i> +</I>>>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend-request at lists.ninenines.eu</A> +</I>>>><i> +</I>>>><i> with the word `help' in the subject or body (don't include the +</I>>>><i> quotes), and you will get back a message with instructions. +</I>>>><i> +</I>>>><i> You must know your password to change your options (including changing +</I>>>><i> the password, itself) or to unsubscribe without confirmation. It is: +</I>>>><i> +</I>>>><i> doofus1 +</I>>>><i> +</I>>>><i> Normally, Mailman will remind you of your lists.ninenines.eu mailing +</I>>>><i> list passwords once every month, although you can disable this if you +</I>>>><i> prefer. This reminder will also include instructions on how to +</I>>>><i> unsubscribe or change your account options. There is also a button on +</I>>>><i> your options page that will email your current password to you. +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>><i> +</I>><i> +</I>><i> +</I>><i>-- +</I>><i>Loïc Hoguin +</I>><i>Erlang Cowboy +</I>><i>Nine Nines +</I>><i><A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I> + + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000105.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI>Next message: <A HREF="000107.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#106">[ date ]</a> + <a href="thread.html#106">[ thread ]</a> + <a href="subject.html#106">[ subject ]</a> + <a href="author.html#106">[ 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/_build/static/archives/extend/2013-April/000107.html b/_build/static/archives/extend/2013-April/000107.html new file mode 100644 index 00000000..dfdb80fa --- /dev/null +++ b/_build/static/archives/extend/2013-April/000107.html @@ -0,0 +1,93 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] populating #http_req for unit testing + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20populating%20%23http_req%20for%20unit%20testing&In-Reply-To=%3CCAKAMJXjXrMs5OR%2BWfHwkmixGAx1UUP4-HyprhTffEjT4yXKBnA%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="000106.html"> + <LINK REL="Next" HREF="000108.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] populating #http_req for unit testing</H1> + <B>Eduardo Gurgel</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20populating%20%23http_req%20for%20unit%20testing&In-Reply-To=%3CCAKAMJXjXrMs5OR%2BWfHwkmixGAx1UUP4-HyprhTffEjT4yXKBnA%40mail.gmail.com%3E" + TITLE="[99s-extend] populating #http_req for unit testing">edgurgel at gmail.com + </A><BR> + <I>Sat Apr 13 13:12:39 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000106.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI>Next message: <A HREF="000108.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#107">[ date ]</a> + <a href="thread.html#107">[ thread ]</a> + <a href="subject.html#107">[ subject ]</a> + <a href="author.html#107">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thu, Apr 11, 2013 at 8:37 PM, Brown, Kevin <<A HREF="https://lists.ninenines.eu/listinfo/extend">Kevin.Brown at turner.com</A>>wrote: + +><i> +</I>><i> Cowfolk, +</I>><i> +</I>><i> I am doing something like this to create an #http_req suitable for unit +</I>><i> testing my resource callbacks: +</I>><i> +</I> + +I use the library meck(<A HREF="https://github.com/eproxus/meck">https://github.com/eproxus/meck</A>) to test stuff doing +something like this: + +some_test() -> + meck:expect(cowboy_req, binding, 2, {<<"app_key">>, req} ) + ?assertEqual({ok, req, empty}, + websocket_handler:websocket_init(transport, req, opts)), + ?assert(meck:validate(cowboy_req)). + +I use simple atoms as input and mock the cowboy_req functions to return +atoms that would represent the correct or the wrong answer. + +The real implementation or how cowboy represent stuff is not important +here, just the output pattern like {Binding, Req}. + +That's it + +-- + +Eduardo +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20130413/f1b70800/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130413/f1b70800/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000106.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI>Next message: <A HREF="000108.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#107">[ date ]</a> + <a href="thread.html#107">[ thread ]</a> + <a href="subject.html#107">[ subject ]</a> + <a href="author.html#107">[ 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/_build/static/archives/extend/2013-April/000108.html b/_build/static/archives/extend/2013-April/000108.html new file mode 100644 index 00000000..b5cf96b3 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000108.html @@ -0,0 +1,88 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Reading body_qs multiple times + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Reading%20body_qs%20multiple%20times&In-Reply-To=%3CCAJ0zLRN-62a9P7QhGz5q6qoj4WaWGv_4qzEznzzwb07Hqo-0QQ%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="000107.html"> + <LINK REL="Next" HREF="000109.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Reading body_qs multiple times</H1> + <B>rambocoder</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Reading%20body_qs%20multiple%20times&In-Reply-To=%3CCAJ0zLRN-62a9P7QhGz5q6qoj4WaWGv_4qzEznzzwb07Hqo-0QQ%40mail.gmail.com%3E" + TITLE="[99s-extend] Reading body_qs multiple times">erlang at rambocoder.com + </A><BR> + <I>Mon Apr 15 22:45:42 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000107.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI>Next message: <A HREF="000109.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#108">[ date ]</a> + <a href="thread.html#108">[ thread ]</a> + <a href="subject.html#108">[ subject ]</a> + <a href="author.html#108">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello group, + +I am trying to put together a CSRF middleware +<A HREF="https://github.com/rambocoder/stable/commit/b26980d292ac42aadfe9921a961436e28cdbb693">https://github.com/rambocoder/stable/commit/b26980d292ac42aadfe9921a961436e28cdbb693</A> +and +if the body of the request contains "_csrf" token, I check to make sure it +matches the csrf token in the session. + +Currently I am doing it in middleware using cowboy_req:body_qs/1 however +when in the handler I need to read another body parameter, such as in the +rest_pastebin example: + +{ok, BodyQs, Req3} = cowboy_req:body_qs(Req), +Paste = proplists:get_value(<<"paste">>, BodyQs), + +cowboy_req:body_qs/1 returns [] due to the body of the request being +already read {body_state,done} + +Is it pointless to have the type of CSRF middleware that I am writing and +just do the CSRF in the handler's callback, where I can deal with all the +body_qs at once? + +Thank you, + +rambocoder +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20130415/03f35a62/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130415/03f35a62/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000107.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI>Next message: <A HREF="000109.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#108">[ date ]</a> + <a href="thread.html#108">[ thread ]</a> + <a href="subject.html#108">[ subject ]</a> + <a href="author.html#108">[ 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/_build/static/archives/extend/2013-April/000109.html b/_build/static/archives/extend/2013-April/000109.html new file mode 100644 index 00000000..4d048b76 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000109.html @@ -0,0 +1,104 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Reading body_qs multiple times + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Reading%20body_qs%20multiple%20times&In-Reply-To=%3C516C6773.1000004%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="000108.html"> + <LINK REL="Next" HREF="000110.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Reading body_qs multiple times</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Reading%20body_qs%20multiple%20times&In-Reply-To=%3C516C6773.1000004%40ninenines.eu%3E" + TITLE="[99s-extend] Reading body_qs multiple times">essen at ninenines.eu + </A><BR> + <I>Mon Apr 15 22:47:47 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000108.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI>Next message: <A HREF="000110.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#109">[ date ]</a> + <a href="thread.html#109">[ thread ]</a> + <a href="subject.html#109">[ subject ]</a> + <a href="author.html#109">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Why not just put the token in the URL instead? if it's CSRF then it's +probably used only once and only for POST and the like, so not cached or +anything. + +On 04/15/2013 10:45 PM, rambocoder wrote: +><i> Hello group, +</I>><i> +</I>><i> I am trying to put together a CSRF middleware +</I>><i> <A HREF="https://github.com/rambocoder/stable/commit/b26980d292ac42aadfe9921a961436e28cdbb693">https://github.com/rambocoder/stable/commit/b26980d292ac42aadfe9921a961436e28cdbb693</A> and +</I>><i> if the body of the request contains "_csrf" token, I check to make sure +</I>><i> it matches the csrf token in the session. +</I>><i> +</I>><i> Currently I am doing it in middleware using cowboy_req:body_qs/1 however +</I>><i> when in the handler I need to read another body parameter, such as in +</I>><i> the rest_pastebin example: +</I>><i> +</I>><i> {ok, BodyQs, Req3} = cowboy_req:body_qs(Req), +</I>><i> Paste = proplists:get_value(<<"paste">>, BodyQs), +</I>><i> +</I>><i> cowboy_req:body_qs/1 returns [] due to the body of the request being +</I>><i> already read {body_state,done} +</I>><i> +</I>><i> Is it pointless to have the type of CSRF middleware that I am writing +</I>><i> and just do the CSRF in the handler's callback, where I can deal with +</I>><i> all the body_qs at once? +</I>><i> +</I>><i> Thank you, +</I>><i> +</I>><i> rambocoder +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I> + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000108.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI>Next message: <A HREF="000110.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#109">[ date ]</a> + <a href="thread.html#109">[ thread ]</a> + <a href="subject.html#109">[ subject ]</a> + <a href="author.html#109">[ 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/_build/static/archives/extend/2013-April/000110.html b/_build/static/archives/extend/2013-April/000110.html new file mode 100644 index 00000000..7bf621ee --- /dev/null +++ b/_build/static/archives/extend/2013-April/000110.html @@ -0,0 +1,149 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Reading body_qs multiple times + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Reading%20body_qs%20multiple%20times&In-Reply-To=%3CCAJ0zLRPYmtXEMd6G78D5Dc9-ebrdRzxyWmVHnzGE%3DYrH%2BhA6fg%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="000109.html"> + <LINK REL="Next" HREF="000111.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Reading body_qs multiple times</H1> + <B>rambocoder</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Reading%20body_qs%20multiple%20times&In-Reply-To=%3CCAJ0zLRPYmtXEMd6G78D5Dc9-ebrdRzxyWmVHnzGE%3DYrH%2BhA6fg%40mail.gmail.com%3E" + TITLE="[99s-extend] Reading body_qs multiple times">erlang at rambocoder.com + </A><BR> + <I>Tue Apr 16 02:13:44 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000109.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI>Next message: <A HREF="000111.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#110">[ date ]</a> + <a href="thread.html#110">[ thread ]</a> + <a href="subject.html#110">[ subject ]</a> + <a href="author.html#110">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Loic, + +After giving the CSRF middleware some thought and reading +<A HREF="https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF">https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF</A>)_Prevention_Cheat_Sheet#Disclosure_of_Token_in_URL +I +came to conclusion that it is best to just not create the middleware and +instead deal with CSRF on as needed basis. + +I know that node's Connect middleware +<A HREF="http://www.senchalabs.org/connect/csrf.html#defaultValue">http://www.senchalabs.org/connect/csrf.html#defaultValue</A> for example allows +for the csrf token to be passed as a query string parameter, however, the +OWASP article made me think that it is not the most secure approach. + +For example, AngularJS <A HREF="http://docs.angularjs.org/api/ng.$http">http://docs.angularjs.org/api/ng.$http</A> has a section +on how their AJAX component behaves to do CSRF out of the box, and they are +talking about the server sending a cookie XSRF-TOKEN that is not HttpOnly. +That makes me realize that csrf is a process more than just slapping some +middleware into the pipeline. + +Btw, I noticed that when the result of the middleware execute function is: +{error, StatusCode, Req} +if I set the reply on the request via cowboy_req:reply before returning the +{error.. , the status code of that reply will be used. + +Such as: +{ok, Req3} = cowboy_req:reply(403, [], "Invalid CSRF Token.", Req2), +{error, 500, Req3}; % 500 is ignored, 403 is returned + +Is that by design? + +Sincerely, + +rambocoder + + + +On Mon, Apr 15, 2013 at 4:47 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> wrote: + +><i> Why not just put the token in the URL instead? if it's CSRF then it's +</I>><i> probably used only once and only for POST and the like, so not cached or +</I>><i> anything. +</I>><i> +</I>><i> +</I>><i> On 04/15/2013 10:45 PM, rambocoder wrote: +</I>><i> +</I>>><i> Hello group, +</I>>><i> +</I>>><i> I am trying to put together a CSRF middleware +</I>>><i> <A HREF="https://github.com/rambocoder/**stable/commit/**">https://github.com/rambocoder/**stable/commit/**</A> +</I>>><i> b26980d292ac42aadfe9921a961436**e28cdbb693<<A HREF="https://github.com/rambocoder/stable/commit/b26980d292ac42aadfe9921a961436e28cdbb693">https://github.com/rambocoder/stable/commit/b26980d292ac42aadfe9921a961436e28cdbb693</A>>and +</I>>><i> if the body of the request contains "_csrf" token, I check to make sure +</I>>><i> it matches the csrf token in the session. +</I>>><i> +</I>>><i> Currently I am doing it in middleware using cowboy_req:body_qs/1 however +</I>>><i> when in the handler I need to read another body parameter, such as in +</I>>><i> the rest_pastebin example: +</I>>><i> +</I>>><i> {ok, BodyQs, Req3} = cowboy_req:body_qs(Req), +</I>>><i> Paste = proplists:get_value(<<"paste">**>, BodyQs), +</I>>><i> +</I>>><i> cowboy_req:body_qs/1 returns [] due to the body of the request being +</I>>><i> already read {body_state,done} +</I>>><i> +</I>>><i> Is it pointless to have the type of CSRF middleware that I am writing +</I>>><i> and just do the CSRF in the handler's callback, where I can deal with +</I>>><i> all the body_qs at once? +</I>>><i> +</I>>><i> Thank you, +</I>>><i> +</I>>><i> rambocoder +</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="http://lists.ninenines.eu:81/**listinfo/extend<http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/**listinfo/extend<http://lists.ninenines.eu:81/listinfo/extend</A>> +</I>>><i> +</I>>><i> +</I>><i> +</I>><i> -- +</I>><i> Loďc Hoguin +</I>><i> Erlang Cowboy +</I>><i> Nine Nines +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I>><i> +</I>-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20130415/59aaeef2/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130415/59aaeef2/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000109.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI>Next message: <A HREF="000111.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#110">[ date ]</a> + <a href="thread.html#110">[ thread ]</a> + <a href="subject.html#110">[ subject ]</a> + <a href="author.html#110">[ 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/_build/static/archives/extend/2013-April/000111.html b/_build/static/archives/extend/2013-April/000111.html new file mode 100644 index 00000000..95e1e1f5 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000111.html @@ -0,0 +1,165 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Reading body_qs multiple times + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Reading%20body_qs%20multiple%20times&In-Reply-To=%3C516D3736.4000106%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="000110.html"> + <LINK REL="Next" HREF="000112.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Reading body_qs multiple times</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Reading%20body_qs%20multiple%20times&In-Reply-To=%3C516D3736.4000106%40ninenines.eu%3E" + TITLE="[99s-extend] Reading body_qs multiple times">essen at ninenines.eu + </A><BR> + <I>Tue Apr 16 13:34:14 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000110.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI>Next message: <A HREF="000112.html">[99s-extend] Cowboy CORS +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#111">[ date ]</a> + <a href="thread.html#111">[ thread ]</a> + <a href="subject.html#111">[ subject ]</a> + <a href="author.html#111">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 04/16/2013 02:13 AM, rambocoder wrote: +><i> Loic, +</I>><i> +</I>><i> After giving the CSRF middleware some thought and reading +</I>><i> <A HREF="https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF">https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF</A>)_Prevention_Cheat_Sheet#Disclosure_of_Token_in_URL I +</I>><i> came to conclusion that it is best to just not create the middleware and +</I>><i> instead deal with CSRF on as needed basis. +</I> +Your link says what I said too, except I probably wasn't explicit enough. + +If you have a form that does POST (or PUT or PATCH or DELETE), put the +token in "<form action="/path/to/resource?csrf=$TOKEN">". The token must +be only valid once, it must not be reused, not even between different +forms (each form gets its own token). Since it is not a GET request, +then you don't have cache or referer issues. + +You can still have issues if you allow another site to run JS on yours +(but you probably shouldn't) or if there is a malevolent proxy (use SSL +where needed), but these are different issues entirely. + +><i> Btw, I noticed that when the result of the middleware execute function is: +</I>><i> {error, StatusCode, Req} +</I>><i> if I set the reply on the request via cowboy_req:reply before returning +</I>><i> the {error.. , the status code of that reply will be used. +</I>><i> +</I>><i> Such as: +</I>><i> {ok, Req3} = cowboy_req:reply(403, [], "Invalid CSRF Token.", Req2), +</I>><i> {error, 500, Req3}; % 500 is ignored, 403 is returned +</I> +Yes, the response was already sent, therefore the second one is ignored. + +><i> Is that by design? +</I>><i> +</I>><i> Sincerely, +</I>><i> +</I>><i> rambocoder +</I>><i> +</I>><i> +</I>><i> +</I>><i> On Mon, Apr 15, 2013 at 4:47 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> Why not just put the token in the URL instead? if it's CSRF then +</I>><i> it's probably used only once and only for POST and the like, so not +</I>><i> cached or anything. +</I>><i> +</I>><i> +</I>><i> On 04/15/2013 10:45 PM, rambocoder wrote: +</I>><i> +</I>><i> Hello group, +</I>><i> +</I>><i> I am trying to put together a CSRF middleware +</I>><i> <A HREF="https://github.com/rambocoder/__stable/commit/__b26980d292ac42aadfe9921a961436__e28cdbb693">https://github.com/rambocoder/__stable/commit/__b26980d292ac42aadfe9921a961436__e28cdbb693</A> +</I>><i> <<A HREF="https://github.com/rambocoder/stable/commit/b26980d292ac42aadfe9921a961436e28cdbb693">https://github.com/rambocoder/stable/commit/b26980d292ac42aadfe9921a961436e28cdbb693</A>> +</I>><i> and +</I>><i> if the body of the request contains "_csrf" token, I check to +</I>><i> make sure +</I>><i> it matches the csrf token in the session. +</I>><i> +</I>><i> Currently I am doing it in middleware using cowboy_req:body_qs/1 +</I>><i> however +</I>><i> when in the handler I need to read another body parameter, such +</I>><i> as in +</I>><i> the rest_pastebin example: +</I>><i> +</I>><i> {ok, BodyQs, Req3} = cowboy_req:body_qs(Req), +</I>><i> Paste = proplists:get_value(<<"paste">__>, BodyQs), +</I>><i> +</I>><i> cowboy_req:body_qs/1 returns [] due to the body of the request being +</I>><i> already read {body_state,done} +</I>><i> +</I>><i> Is it pointless to have the type of CSRF middleware that I am +</I>><i> writing +</I>><i> and just do the CSRF in the handler's callback, where I can deal +</I>><i> with +</I>><i> all the body_qs at once? +</I>><i> +</I>><i> Thank you, +</I>><i> +</I>><i> rambocoder +</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="http://lists.ninenines.eu:81/__listinfo/extend">http://lists.ninenines.eu:81/__listinfo/extend</A> +</I>><i> <<A HREF="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A>> +</I>><i> +</I>><i> +</I>><i> +</I>><i> -- +</I>><i> Loďc Hoguin +</I>><i> Erlang Cowboy +</I>><i> Nine Nines +</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A> +</I>><i> +</I>><i> +</I> + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000110.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI>Next message: <A HREF="000112.html">[99s-extend] Cowboy CORS +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#111">[ date ]</a> + <a href="thread.html#111">[ thread ]</a> + <a href="subject.html#111">[ subject ]</a> + <a href="author.html#111">[ 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/_build/static/archives/extend/2013-April/000112.html b/_build/static/archives/extend/2013-April/000112.html new file mode 100644 index 00000000..d2d82a89 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000112.html @@ -0,0 +1,119 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Cowboy CORS + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%20CORS&In-Reply-To=%3C0103B45C-A73C-498E-908D-AA1639D3DEE1%40gmail.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="000111.html"> + <LINK REL="Next" HREF="000113.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Cowboy CORS</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%20CORS&In-Reply-To=%3C0103B45C-A73C-498E-908D-AA1639D3DEE1%40gmail.com%3E" + TITLE="[99s-extend] Cowboy CORS">lee.sylvester at gmail.com + </A><BR> + <I>Fri Apr 19 16:47:09 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000111.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI>Next message: <A HREF="000113.html">[99s-extend] Cowboy CORS +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#112">[ date ]</a> + <a href="thread.html#112">[ thread ]</a> + <a href="subject.html#112">[ subject ]</a> + <a href="author.html#112">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi guys, + +So, I thought I had this resolved, as I managed to get it working locally, but across different local domains (test.localhost.com and cowboy.localhost.com). However, now I've deployed my app to a VM, I simply can't get CORS working in Cowboy. Here's the OPTIONS response from Chrome's console: + + +Request URL:<A HREF="http://www.example.com/">http://www.example.com/</A> +Request Method:OPTIONS +Status Code:200 OK +Request Headersview source +Accept:*/* +Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +Accept-Encoding:gzip,deflate,sdch +Accept-Language:en-US,en;q=0.8 +Access-Control-Request-Headers:origin, method, content-type +Access-Control-Request-Method:POST +Connection:keep-alive +Host:www.example.com +Origin:<A HREF="http://test.localhost.com:8889">http://test.localhost.com:8889</A> +Referer:<A HREF="http://test.localhost.com:8889/">http://test.localhost.com:8889/</A> +User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 +Response Headersview source +Access-Control-Allow-Headers:Content-Type, X-Requested-With, Origin, Method +Access-Control-Allow-Methods:GET, POST, OPTIONS +Access-Control-Allow-Origin:* +connection:keep-alive +content-length:0 +date:Fri, 19 Apr 2013 14:40:00 GMT +server:Cowboy + +And then this is the POST response: + +Request URL:<A HREF="http://www.example.com/">http://www.example.com/</A> +Request Headersview parsed +POST <A HREF="http://www.example.com/">http://www.example.com/</A> HTTP/1.1 +Origin: <A HREF="http://test.localhost.com:8889">http://test.localhost.com:8889</A> +Referer: <A HREF="http://test.localhost.com:8889/">http://test.localhost.com:8889/</A> +method: POST <A HREF="http://www.example.com/">http://www.example.com/</A> HTTP/1.1 +User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 +content-type: application/x-www-form-urlencoded +Form Dataview parsed +data={"Type":"auth_request","Authentication":"public","Authorization":null,"Domain":"www.example.com","Application":"test_app","Ident":"lee"} + +I am setting {<<"Access-Control-Allow-Origin">>, <<"*">>} in the headers param of cowboy_req:reply and the cowboy_req:set_resp_header, but neither seems to be working. Can anyone spot what I might be doing wrong? + +The cowboy_req:set_resp_header is happening in the handle… So + +handle(Req, State) -> + Reply = case cowboy_req:method(Req) of + {<<"POST">>, Req2} -> + Req3 = cowboy_req:set_resp_header(<<"Access-Control-Allow-Origin">>, <<"*">>, Req2), +[snip] + + +Thanks, +Lee + +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20130419/bf0e8ef9/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130419/bf0e8ef9/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000111.html">[99s-extend] Reading body_qs multiple times +</A></li> + <LI>Next message: <A HREF="000113.html">[99s-extend] Cowboy CORS +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#112">[ date ]</a> + <a href="thread.html#112">[ thread ]</a> + <a href="subject.html#112">[ subject ]</a> + <a href="author.html#112">[ 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/_build/static/archives/extend/2013-April/000113.html b/_build/static/archives/extend/2013-April/000113.html new file mode 100644 index 00000000..26913530 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000113.html @@ -0,0 +1,172 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Cowboy CORS + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%20CORS&In-Reply-To=%3CCD96D43A.4E43%25christopher.phillips%40turner.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="000112.html"> + <LINK REL="Next" HREF="000114.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Cowboy CORS</H1> + <B>Phillips, Christopher</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%20CORS&In-Reply-To=%3CCD96D43A.4E43%25christopher.phillips%40turner.com%3E" + TITLE="[99s-extend] Cowboy CORS">Christopher.Phillips at turner.com + </A><BR> + <I>Fri Apr 19 17:08:03 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000112.html">[99s-extend] Cowboy CORS +</A></li> + <LI>Next message: <A HREF="000114.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#113">[ date ]</a> + <a href="thread.html#113">[ thread ]</a> + <a href="subject.html#113">[ subject ]</a> + <a href="author.html#113">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> When querying to the VM from a browser, is Chrome complaining that it's a cross domain request in the console? Or something else? + + Is the OPTIONS request firing and failing, or is it the POST that is failing (in the network tab)? + + If it's working in a cross origin context for you locally across different domains (I.e., the browser is sending the CORS headers on the request, and you're seeing the right headers on the response, and the browser is handling them properly, such that you can retrieve the response from your Javascript), then it seems unlikely to be a CORS issue, but maybe a config or proxy or code issue in your handler. + + +From: Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A><mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>>> +Date: Friday, April 19, 2013 10:47 AM +To: "<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>>" <<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>>> +Subject: [99s-extend] Cowboy CORS + +Hi guys, + +So, I thought I had this resolved, as I managed to get it working locally, but across different local domains (test.localhost.com<<A HREF="http://test.localhost.com">http://test.localhost.com</A>> and cowboy.localhost.com<<A HREF="http://cowboy.localhost.com">http://cowboy.localhost.com</A>>). However, now I've deployed my app to a VM, I simply can't get CORS working in Cowboy. Here's the OPTIONS response from Chrome's console: + + + + 1. +Request URL: +<A HREF="http://www.example.com/">http://www.example.com/</A> + 2. +Request Method: +OPTIONS + 3. +Status Code: +200 OK + 4. Request Headersview source + * +Accept: +*/* + * +Accept-Charset: +ISO-8859-1,utf-8;q=0.7,*;q=0.3 + * +Accept-Encoding: +gzip,deflate,sdch + * +Accept-Language: +en-US,en;q=0.8 + * +Access-Control-Request-Headers: +origin, method, content-type + * +Access-Control-Request-Method: +POST + * +Connection: +keep-alive + * +Host: +www.example.com<<A HREF="http://www.example.com">http://www.example.com</A>> + * +Origin: +<A HREF="http://test.localhost.com:8889">http://test.localhost.com:8889</A> + * +Referer: +<A HREF="http://test.localhost.com:8889/">http://test.localhost.com:8889/</A> + * +User-Agent: +Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 + 5. Response Headersview source + * +Access-Control-Allow-Headers: +Content-Type, X-Requested-With, Origin, Method + * +Access-Control-Allow-Methods: +GET, POST, OPTIONS + * +Access-Control-Allow-Origin: +* + * +connection: +keep-alive + * +content-length: +0 + * +date: +Fri, 19 Apr 2013 14:40:00 GMT + * +server: +Cowboy + +And then this is the POST response: + + + 1. +Request URL: +<A HREF="http://www.example.com/">http://www.example.com/</A> + 2. Request Headersview parsed + * POST <A HREF="http://www.example.com/">http://www.example.com/</A> HTTP/1.1 Origin: <A HREF="http://test.localhost.com:8889">http://test.localhost.com:8889</A> Referer: <A HREF="http://test.localhost.com:8889/">http://test.localhost.com:8889/</A> method: POST <A HREF="http://www.example.com/">http://www.example.com/</A> HTTP/1.1 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 content-type: application/x-www-form-urlencoded + 3. Form Dataview parsed + * data={"Type":"auth_request","Authentication":"public","Authorization":null,"Domain":"www.example.com<<A HREF="http://www.example.com">http://www.example.com</A>>","Application":"test_app","Ident":"lee"} + +I am setting {<<"Access-Control-Allow-Origin">>, <<"*">>} in the headers param of cowboy_req:reply and the cowboy_req:set_resp_header, but neither seems to be working. Can anyone spot what I might be doing wrong? + +The cowboy_req:set_resp_header is happening in the handle… So + +handle(Req, State) -> +Reply = case cowboy_req:method(Req) of +{<<"POST">>, Req2} -> +Req3 = cowboy_req:set_resp_header(<<"Access-Control-Allow-Origin">>, <<"*">>, Req2), +[snip] + + +Thanks, +Lee + +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20130419/383515dd/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130419/383515dd/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000112.html">[99s-extend] Cowboy CORS +</A></li> + <LI>Next message: <A HREF="000114.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#113">[ date ]</a> + <a href="thread.html#113">[ thread ]</a> + <a href="subject.html#113">[ subject ]</a> + <a href="author.html#113">[ 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/_build/static/archives/extend/2013-April/000114.html b/_build/static/archives/extend/2013-April/000114.html new file mode 100644 index 00000000..9f107a90 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000114.html @@ -0,0 +1,98 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] 505 error + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C7E836341-BC4B-4575-AAFC-9F610A5610AE%40gmail.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="000113.html"> + <LINK REL="Next" HREF="000115.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] 505 error</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C7E836341-BC4B-4575-AAFC-9F610A5610AE%40gmail.com%3E" + TITLE="[99s-extend] 505 error">lee.sylvester at gmail.com + </A><BR> + <I>Mon Apr 22 14:59:54 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000113.html">[99s-extend] Cowboy CORS +</A></li> + <LI>Next message: <A HREF="000115.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#114">[ date ]</a> + <a href="thread.html#114">[ thread ]</a> + <a href="subject.html#114">[ subject ]</a> + <a href="author.html#114">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi guys, + +So, I was getting a CORS issue when connecting to my Bullet impl, which I have since fixed. I am now able to use these from many machines from many locations. However, I have found some machines to be getting a 505 error when making a POST request to the Cowboy instance: + +Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +Request Method:OPTIONS +Status Code:505 HTTP Version Not Supported +Request Headersview source +Accept:*/* +Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +Accept-Encoding:gzip,deflate,sdch +Accept-Language:en-US,en;q=0.8 +Access-Control-Request-Headers:origin, method, content-type +Access-Control-Request-Method:POST +Connection:keep-alive +Host:www.example.com +Origin:<A HREF="http://www.test.com">http://www.test.com</A> +Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31 +Response Headersview source +connection:close +content-length:0 +date:Mon, 22 Apr 2013 12:22:50 GMT +server:Cowboy + +To get around the CORS issue, I set up an onrequest hook, which points to the function: + +set_request_cors(Req) -> + Req2 = cowboy_req:set_resp_header(<<"Access-Control-Allow-Methods">>, <<"GET, POST, OPTIONS">>, Req), + Req3 = cowboy_req:set_resp_header(<<"Access-Control-Allow-Headers">>, <<"Content-Type, X-Requested-With, Origin, Method">>, Req2), + cowboy_req:set_resp_header(<<"Access-Control-Allow-Origin">>, <<"*">>, Req3). + +I'm afraid I don't have any more info, but this issue is completely eluding me. + +Thanks, +Lee + + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000113.html">[99s-extend] Cowboy CORS +</A></li> + <LI>Next message: <A HREF="000115.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#114">[ date ]</a> + <a href="thread.html#114">[ thread ]</a> + <a href="subject.html#114">[ subject ]</a> + <a href="author.html#114">[ 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/_build/static/archives/extend/2013-April/000115.html b/_build/static/archives/extend/2013-April/000115.html new file mode 100644 index 00000000..e6e5ba97 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000115.html @@ -0,0 +1,110 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] 505 error + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C74D3D8EB-2285-47F5-9BD9-BED2021BE79A%40turner.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="000114.html"> + <LINK REL="Next" HREF="000116.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] 505 error</H1> + <B>Brown, Kevin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C74D3D8EB-2285-47F5-9BD9-BED2021BE79A%40turner.com%3E" + TITLE="[99s-extend] 505 error">Kevin.Brown at turner.com + </A><BR> + <I>Mon Apr 22 16:28:11 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000114.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000116.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#115">[ date ]</a> + <a href="thread.html#115">[ thread ]</a> + <a href="subject.html#115">[ subject ]</a> + <a href="author.html#115">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>What is the exact http request sent on the failing and successful machines? How do the differ? + +Stack trace? + +On Apr 22, 2013, at 9:00 AM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: + +><i> Hi guys, +</I>><i> +</I>><i> So, I was getting a CORS issue when connecting to my Bullet impl, which I have since fixed. I am now able to use these from many machines from many locations. However, I have found some machines to be getting a 505 error when making a POST request to the Cowboy instance: +</I>><i> +</I>><i> Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>><i> Request Method:OPTIONS +</I>><i> Status Code:505 HTTP Version Not Supported +</I>><i> Request Headersview source +</I>><i> Accept:*/* +</I>><i> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>><i> Accept-Encoding:gzip,deflate,sdch +</I>><i> Accept-Language:en-US,en;q=0.8 +</I>><i> Access-Control-Request-Headers:origin, method, content-type +</I>><i> Access-Control-Request-Method:POST +</I>><i> Connection:keep-alive +</I>><i> Host:www.example.com +</I>><i> Origin:<A HREF="http://www.test.com">http://www.test.com</A> +</I>><i> Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +</I>><i> User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31 +</I>><i> Response Headersview source +</I>><i> connection:close +</I>><i> content-length:0 +</I>><i> date:Mon, 22 Apr 2013 12:22:50 GMT +</I>><i> server:Cowboy +</I>><i> +</I>><i> To get around the CORS issue, I set up an onrequest hook, which points to the function: +</I>><i> +</I>><i> set_request_cors(Req) -> +</I>><i> Req2 = cowboy_req:set_resp_header(<<"Access-Control-Allow-Methods">>, <<"GET, POST, OPTIONS">>, Req), +</I>><i> Req3 = cowboy_req:set_resp_header(<<"Access-Control-Allow-Headers">>, <<"Content-Type, X-Requested-With, Origin, Method">>, Req2), +</I>><i> cowboy_req:set_resp_header(<<"Access-Control-Allow-Origin">>, <<"*">>, Req3). +</I>><i> +</I>><i> I'm afraid I don't have any more info, but this issue is completely eluding me. +</I>><i> +</I>><i> Thanks, +</I>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000114.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000116.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#115">[ date ]</a> + <a href="thread.html#115">[ thread ]</a> + <a href="subject.html#115">[ subject ]</a> + <a href="author.html#115">[ 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/_build/static/archives/extend/2013-April/000116.html b/_build/static/archives/extend/2013-April/000116.html new file mode 100644 index 00000000..0375b7de --- /dev/null +++ b/_build/static/archives/extend/2013-April/000116.html @@ -0,0 +1,151 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] 505 error + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C8D420762-BBE6-48AC-81C9-56FED6EDA3F2%40gmail.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="000115.html"> + <LINK REL="Next" HREF="000117.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] 505 error</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C8D420762-BBE6-48AC-81C9-56FED6EDA3F2%40gmail.com%3E" + TITLE="[99s-extend] 505 error">lee.sylvester at gmail.com + </A><BR> + <I>Mon Apr 22 16:40:19 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000115.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000117.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#116">[ date ]</a> + <a href="thread.html#116">[ thread ]</a> + <a href="subject.html#116">[ subject ]</a> + <a href="author.html#116">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Well, the below is the sent and return headers on the failing machine. On a succeeding machine, the headers are + +Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +Request Method:OPTIONS +Status Code:200 OK + +Request Headersview source +Accept:*/* +Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +Accept-Encoding:gzip,deflate,sdch +Accept-Language:en-US,en;q=0.8 +Access-Control-Request-Headers:origin, method, content-type +Access-Control-Request-Method:POST +Connection:keep-alive +Host:www.example.com +Origin:<A HREF="http://www.test.com">http://www.test.com</A> +Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 + +Response Headersview source +Access-Control-Allow-Headers:Content-Type, X-Requested-With, Origin, Method +Access-Control-Allow-Methods:GET, POST, OPTIONS +Access-Control-Allow-Origin:* +connection:keep-alive +content-length:68 +date:Mon, 22 Apr 2013 14:33:30 GMT +server:Cowboy + +As you can see, the header control and content isn't being sent back and the connection is closed. + +Thanks, +Lee + + + + +On 22 Apr 2013, at 15:28, "Brown, Kevin" <<A HREF="https://lists.ninenines.eu/listinfo/extend">Kevin.Brown at turner.com</A>> wrote: + +><i> What is the exact http request sent on the failing and successful machines? How do the differ? +</I>><i> +</I>><i> Stack trace? +</I>><i> +</I>><i> On Apr 22, 2013, at 9:00 AM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>><i> +</I>>><i> Hi guys, +</I>>><i> +</I>>><i> So, I was getting a CORS issue when connecting to my Bullet impl, which I have since fixed. I am now able to use these from many machines from many locations. However, I have found some machines to be getting a 505 error when making a POST request to the Cowboy instance: +</I>>><i> +</I>>><i> Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>>><i> Request Method:OPTIONS +</I>>><i> Status Code:505 HTTP Version Not Supported +</I>>><i> +</I>>><i> Request Headersview source +</I>>><i> Accept:*/* +</I>>><i> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>>><i> Accept-Encoding:gzip,deflate,sdch +</I>>><i> Accept-Language:en-US,en;q=0.8 +</I>>><i> Access-Control-Request-Headers:origin, method, content-type +</I>>><i> Access-Control-Request-Method:POST +</I>>><i> Connection:keep-alive +</I>>><i> Host:www.example.com +</I>>><i> Origin:<A HREF="http://www.test.com">http://www.test.com</A> +</I>>><i> Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +</I>>><i> User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31 +</I>>><i> +</I>>><i> Response Headersview source +</I>>><i> connection:close +</I>>><i> content-length:0 +</I>>><i> date:Mon, 22 Apr 2013 12:22:50 GMT +</I>>><i> server:Cowboy +</I>>><i> +</I>>><i> To get around the CORS issue, I set up an onrequest hook, which points to the function: +</I>>><i> +</I>>><i> set_request_cors(Req) -> +</I>>><i> Req2 = cowboy_req:set_resp_header(<<"Access-Control-Allow-Methods">>, <<"GET, POST, OPTIONS">>, Req), +</I>>><i> Req3 = cowboy_req:set_resp_header(<<"Access-Control-Allow-Headers">>, <<"Content-Type, X-Requested-With, Origin, Method">>, Req2), +</I>>><i> cowboy_req:set_resp_header(<<"Access-Control-Allow-Origin">>, <<"*">>, Req3). +</I>>><i> +</I>>><i> I'm afraid I don't have any more info, but this issue is completely eluding me. +</I>>><i> +</I>>><i> Thanks, +</I>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>><i> +</I>><i> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000115.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000117.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#116">[ date ]</a> + <a href="thread.html#116">[ thread ]</a> + <a href="subject.html#116">[ subject ]</a> + <a href="author.html#116">[ 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/_build/static/archives/extend/2013-April/000117.html b/_build/static/archives/extend/2013-April/000117.html new file mode 100644 index 00000000..12ba1f47 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000117.html @@ -0,0 +1,166 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] 505 error + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C51755D08.2070006%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="000116.html"> + <LINK REL="Next" HREF="000118.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] 505 error</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C51755D08.2070006%40ninenines.eu%3E" + TITLE="[99s-extend] 505 error">essen at ninenines.eu + </A><BR> + <I>Mon Apr 22 17:53:44 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000116.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000118.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#117">[ date ]</a> + <a href="thread.html#117">[ thread ]</a> + <a href="subject.html#117">[ subject ]</a> + <a href="author.html#117">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Headers are one thing but it'd be useful to know the request line itself. + +On 04/22/2013 04:40 PM, Lee Sylvester wrote: +><i> Well, the below is the sent and return headers on the failing machine. On a succeeding machine, the headers are +</I>><i> +</I>><i> Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>><i> Request Method:OPTIONS +</I>><i> Status Code:200 OK +</I>><i> +</I>><i> Request Headersview source +</I>><i> Accept:*/* +</I>><i> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>><i> Accept-Encoding:gzip,deflate,sdch +</I>><i> Accept-Language:en-US,en;q=0.8 +</I>><i> Access-Control-Request-Headers:origin, method, content-type +</I>><i> Access-Control-Request-Method:POST +</I>><i> Connection:keep-alive +</I>><i> Host:www.example.com +</I>><i> Origin:<A HREF="http://www.test.com">http://www.test.com</A> +</I>><i> Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +</I>><i> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 +</I>><i> +</I>><i> Response Headersview source +</I>><i> Access-Control-Allow-Headers:Content-Type, X-Requested-With, Origin, Method +</I>><i> Access-Control-Allow-Methods:GET, POST, OPTIONS +</I>><i> Access-Control-Allow-Origin:* +</I>><i> connection:keep-alive +</I>><i> content-length:68 +</I>><i> date:Mon, 22 Apr 2013 14:33:30 GMT +</I>><i> server:Cowboy +</I>><i> +</I>><i> As you can see, the header control and content isn't being sent back and the connection is closed. +</I>><i> +</I>><i> Thanks, +</I>><i> Lee +</I>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i> On 22 Apr 2013, at 15:28, "Brown, Kevin" <<A HREF="https://lists.ninenines.eu/listinfo/extend">Kevin.Brown at turner.com</A>> wrote: +</I>><i> +</I>>><i> What is the exact http request sent on the failing and successful machines? How do the differ? +</I>>><i> +</I>>><i> Stack trace? +</I>>><i> +</I>>><i> On Apr 22, 2013, at 9:00 AM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>>><i> +</I>>>><i> Hi guys, +</I>>>><i> +</I>>>><i> So, I was getting a CORS issue when connecting to my Bullet impl, which I have since fixed. I am now able to use these from many machines from many locations. However, I have found some machines to be getting a 505 error when making a POST request to the Cowboy instance: +</I>>>><i> +</I>>>><i> Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>>>><i> Request Method:OPTIONS +</I>>>><i> Status Code:505 HTTP Version Not Supported +</I>>>><i> +</I>>>><i> Request Headersview source +</I>>>><i> Accept:*/* +</I>>>><i> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>>>><i> Accept-Encoding:gzip,deflate,sdch +</I>>>><i> Accept-Language:en-US,en;q=0.8 +</I>>>><i> Access-Control-Request-Headers:origin, method, content-type +</I>>>><i> Access-Control-Request-Method:POST +</I>>>><i> Connection:keep-alive +</I>>>><i> Host:www.example.com +</I>>>><i> Origin:<A HREF="http://www.test.com">http://www.test.com</A> +</I>>>><i> Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +</I>>>><i> User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31 +</I>>>><i> +</I>>>><i> Response Headersview source +</I>>>><i> connection:close +</I>>>><i> content-length:0 +</I>>>><i> date:Mon, 22 Apr 2013 12:22:50 GMT +</I>>>><i> server:Cowboy +</I>>>><i> +</I>>>><i> To get around the CORS issue, I set up an onrequest hook, which points to the function: +</I>>>><i> +</I>>>><i> set_request_cors(Req) -> +</I>>>><i> Req2 = cowboy_req:set_resp_header(<<"Access-Control-Allow-Methods">>, <<"GET, POST, OPTIONS">>, Req), +</I>>>><i> Req3 = cowboy_req:set_resp_header(<<"Access-Control-Allow-Headers">>, <<"Content-Type, X-Requested-With, Origin, Method">>, Req2), +</I>>>><i> cowboy_req:set_resp_header(<<"Access-Control-Allow-Origin">>, <<"*">>, Req3). +</I>>>><i> +</I>>>><i> I'm afraid I don't have any more info, but this issue is completely eluding me. +</I>>>><i> +</I>>>><i> Thanks, +</I>>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I> + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000116.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000118.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#117">[ date ]</a> + <a href="thread.html#117">[ thread ]</a> + <a href="subject.html#117">[ subject ]</a> + <a href="author.html#117">[ 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/_build/static/archives/extend/2013-April/000118.html b/_build/static/archives/extend/2013-April/000118.html new file mode 100644 index 00000000..b9a0d0b2 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000118.html @@ -0,0 +1,178 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] 505 error + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3CCD9AD247.AB02%25kevin.brown%40turner.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="000117.html"> + <LINK REL="Next" HREF="000119.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] 505 error</H1> + <B>Brown, Kevin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3CCD9AD247.AB02%25kevin.brown%40turner.com%3E" + TITLE="[99s-extend] 505 error">Kevin.Brown at turner.com + </A><BR> + <I>Mon Apr 22 17:55:11 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000117.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000119.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#118">[ date ]</a> + <a href="thread.html#118">[ thread ]</a> + <a href="subject.html#118">[ subject ]</a> + <a href="author.html#118">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>You might see if "view source" (rather than the parsed view you sent) +yields any clues. You'd like to see HTTP version being sent. + + +On 4/22/13 10:40 AM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: + +><i>Well, the below is the sent and return headers on the failing machine. +</I>><i>On a succeeding machine, the headers are +</I>><i> +</I>><i>Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>><i>Request Method:OPTIONS +</I>><i>Status Code:200 OK +</I>><i> +</I>><i>Request Headersview source +</I>><i>Accept:*/* +</I>><i>Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>><i>Accept-Encoding:gzip,deflate,sdch +</I>><i>Accept-Language:en-US,en;q=0.8 +</I>><i>Access-Control-Request-Headers:origin, method, content-type +</I>><i>Access-Control-Request-Method:POST +</I>><i>Connection:keep-alive +</I>><i>Host:www.example.com +</I>><i>Origin:<A HREF="http://www.test.com">http://www.test.com</A> +</I>><i>Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +</I>><i>User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) +</I>><i>AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 +</I>><i> +</I>><i>Response Headersview source +</I>><i>Access-Control-Allow-Headers:Content-Type, X-Requested-With, Origin, +</I>><i>Method +</I>><i>Access-Control-Allow-Methods:GET, POST, OPTIONS +</I>><i>Access-Control-Allow-Origin:* +</I>><i>connection:keep-alive +</I>><i>content-length:68 +</I>><i>date:Mon, 22 Apr 2013 14:33:30 GMT +</I>><i>server:Cowboy +</I>><i> +</I>><i>As you can see, the header control and content isn't being sent back and +</I>><i>the connection is closed. +</I>><i> +</I>><i>Thanks, +</I>><i>Lee +</I>><i> +</I>><i> +</I>><i> +</I>><i> +</I>><i>On 22 Apr 2013, at 15:28, "Brown, Kevin" <<A HREF="https://lists.ninenines.eu/listinfo/extend">Kevin.Brown at turner.com</A>> wrote: +</I>><i> +</I>>><i> What is the exact http request sent on the failing and successful +</I>>><i>machines? How do the differ? +</I>>><i> +</I>>><i> Stack trace? +</I>>><i> +</I>>><i> On Apr 22, 2013, at 9:00 AM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> +</I>>><i>wrote: +</I>>><i> +</I>>>><i> Hi guys, +</I>>>><i> +</I>>>><i> So, I was getting a CORS issue when connecting to my Bullet impl, +</I>>>><i>which I have since fixed. I am now able to use these from many +</I>>>><i>machines from many locations. However, I have found some machines to +</I>>>><i>be getting a 505 error when making a POST request to the Cowboy +</I>>>><i>instance: +</I>>>><i> +</I>>>><i> Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>>>><i> Request Method:OPTIONS +</I>>>><i> Status Code:505 HTTP Version Not Supported +</I>>>><i> +</I>>>><i> Request Headersview source +</I>>>><i> Accept:*/* +</I>>>><i> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>>>><i> Accept-Encoding:gzip,deflate,sdch +</I>>>><i> Accept-Language:en-US,en;q=0.8 +</I>>>><i> Access-Control-Request-Headers:origin, method, content-type +</I>>>><i> Access-Control-Request-Method:POST +</I>>>><i> Connection:keep-alive +</I>>>><i> Host:www.example.com +</I>>>><i> Origin:<A HREF="http://www.test.com">http://www.test.com</A> +</I>>>><i> Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +</I>>>><i> User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 +</I>>>><i>(KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31 +</I>>>><i> +</I>>>><i> Response Headersview source +</I>>>><i> connection:close +</I>>>><i> content-length:0 +</I>>>><i> date:Mon, 22 Apr 2013 12:22:50 GMT +</I>>>><i> server:Cowboy +</I>>>><i> +</I>>>><i> To get around the CORS issue, I set up an onrequest hook, which points +</I>>>><i>to the function: +</I>>>><i> +</I>>>><i> set_request_cors(Req) -> +</I>>>><i> Req2 = +</I>>>><i>cowboy_req:set_resp_header(<<"Access-Control-Allow-Methods">>, <<"GET, +</I>>>><i>POST, OPTIONS">>, Req), +</I>>>><i> Req3 = +</I>>>><i>cowboy_req:set_resp_header(<<"Access-Control-Allow-Headers">>, +</I>>>><i><<"Content-Type, X-Requested-With, Origin, Method">>, Req2), +</I>>>><i> cowboy_req:set_resp_header(<<"Access-Control-Allow-Origin">>, +</I>>>><i><<"*">>, Req3). +</I>>>><i> +</I>>>><i> I'm afraid I don't have any more info, but this issue is completely +</I>>>><i>eluding me. +</I>>>><i> +</I>>>><i> Thanks, +</I>>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>>><i> +</I>>><i> +</I>><i> +</I>><i> +</I> + + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000117.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000119.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#118">[ date ]</a> + <a href="thread.html#118">[ thread ]</a> + <a href="subject.html#118">[ subject ]</a> + <a href="author.html#118">[ 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/_build/static/archives/extend/2013-April/000119.html b/_build/static/archives/extend/2013-April/000119.html new file mode 100644 index 00000000..0f58a6e7 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000119.html @@ -0,0 +1,212 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] 505 error + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C5826B1C1-C80E-4073-953C-3BF74829CE1A%40gmail.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="000118.html"> + <LINK REL="Next" HREF="000120.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] 505 error</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C5826B1C1-C80E-4073-953C-3BF74829CE1A%40gmail.com%3E" + TITLE="[99s-extend] 505 error">lee.sylvester at gmail.com + </A><BR> + <I>Mon Apr 22 20:30:08 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000118.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000120.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#119">[ date ]</a> + <a href="thread.html#119">[ thread ]</a> + <a href="subject.html#119">[ subject ]</a> + <a href="author.html#119">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Does this help? + +Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +Request Method:OPTIONS +Status Code:505 HTTP Version Not Supported + +Request Headersview parsed +OPTIONS <A HREF="http://www.example.com">http://www.example.com</A> HTTP/1.1 +Host: www.example.com +Proxy-Connection: keep-alive +Access-Control-Request-Method: POST +Origin: <A HREF="http://localhost">http://localhost</A> +User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31 +Access-Control-Request-Headers: origin, method, content-type +Accept: */* +Referer: <A HREF="http://localhost/p/">http://localhost/p/</A> +Accept-Encoding: gzip,deflate,sdch +Accept-Language: en-US,en;q=0.8 +Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 + +Response Headersview parsed +HTTP/1.1 505 HTTP Version Not Supported +connection: close +server: Cowboy +date: Mon, 22 Apr 2013 17:42:39 GMT +content-length: 0 + +Thanks, +Lee + + +On 22 Apr 2013, at 16:55, "Brown, Kevin" <<A HREF="https://lists.ninenines.eu/listinfo/extend">Kevin.Brown at turner.com</A>> wrote: + +><i> You might see if "view source" (rather than the parsed view you sent) +</I>><i> yields any clues. You'd like to see HTTP version being sent. +</I>><i> +</I>><i> +</I>><i> On 4/22/13 10:40 AM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>><i> +</I>>><i> Well, the below is the sent and return headers on the failing machine. +</I>>><i> On a succeeding machine, the headers are +</I>>><i> +</I>>><i> Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>>><i> Request Method:OPTIONS +</I>>><i> Status Code:200 OK +</I>>><i> +</I>>><i> Request Headersview source +</I>>><i> Accept:*/* +</I>>><i> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>>><i> Accept-Encoding:gzip,deflate,sdch +</I>>><i> Accept-Language:en-US,en;q=0.8 +</I>>><i> Access-Control-Request-Headers:origin, method, content-type +</I>>><i> Access-Control-Request-Method:POST +</I>>><i> Connection:keep-alive +</I>>><i> Host:www.example.com +</I>>><i> Origin:<A HREF="http://www.test.com">http://www.test.com</A> +</I>>><i> Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +</I>>><i> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) +</I>>><i> AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 +</I>>><i> +</I>>><i> Response Headersview source +</I>>><i> Access-Control-Allow-Headers:Content-Type, X-Requested-With, Origin, +</I>>><i> Method +</I>>><i> Access-Control-Allow-Methods:GET, POST, OPTIONS +</I>>><i> Access-Control-Allow-Origin:* +</I>>><i> connection:keep-alive +</I>>><i> content-length:68 +</I>>><i> date:Mon, 22 Apr 2013 14:33:30 GMT +</I>>><i> server:Cowboy +</I>>><i> +</I>>><i> As you can see, the header control and content isn't being sent back and +</I>>><i> the connection is closed. +</I>>><i> +</I>>><i> Thanks, +</I>>><i> Lee +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> +</I>>><i> On 22 Apr 2013, at 15:28, "Brown, Kevin" <<A HREF="https://lists.ninenines.eu/listinfo/extend">Kevin.Brown at turner.com</A>> wrote: +</I>>><i> +</I>>>><i> What is the exact http request sent on the failing and successful +</I>>>><i> machines? How do the differ? +</I>>>><i> +</I>>>><i> Stack trace? +</I>>>><i> +</I>>>><i> On Apr 22, 2013, at 9:00 AM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> +</I>>>><i> wrote: +</I>>>><i> +</I>>>>><i> Hi guys, +</I>>>>><i> +</I>>>>><i> So, I was getting a CORS issue when connecting to my Bullet impl, +</I>>>>><i> which I have since fixed. I am now able to use these from many +</I>>>>><i> machines from many locations. However, I have found some machines to +</I>>>>><i> be getting a 505 error when making a POST request to the Cowboy +</I>>>>><i> instance: +</I>>>>><i> +</I>>>>><i> Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>>>>><i> Request Method:OPTIONS +</I>>>>><i> Status Code:505 HTTP Version Not Supported +</I>>>>><i> +</I>>>>><i> Request Headersview source +</I>>>>><i> Accept:*/* +</I>>>>><i> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>>>>><i> Accept-Encoding:gzip,deflate,sdch +</I>>>>><i> Accept-Language:en-US,en;q=0.8 +</I>>>>><i> Access-Control-Request-Headers:origin, method, content-type +</I>>>>><i> Access-Control-Request-Method:POST +</I>>>>><i> Connection:keep-alive +</I>>>>><i> Host:www.example.com +</I>>>>><i> Origin:<A HREF="http://www.test.com">http://www.test.com</A> +</I>>>>><i> Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +</I>>>>><i> User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 +</I>>>>><i> (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31 +</I>>>>><i> +</I>>>>><i> Response Headersview source +</I>>>>><i> connection:close +</I>>>>><i> content-length:0 +</I>>>>><i> date:Mon, 22 Apr 2013 12:22:50 GMT +</I>>>>><i> server:Cowboy +</I>>>>><i> +</I>>>>><i> To get around the CORS issue, I set up an onrequest hook, which points +</I>>>>><i> to the function: +</I>>>>><i> +</I>>>>><i> set_request_cors(Req) -> +</I>>>>><i> Req2 = +</I>>>>><i> cowboy_req:set_resp_header(<<"Access-Control-Allow-Methods">>, <<"GET, +</I>>>>><i> POST, OPTIONS">>, Req), +</I>>>>><i> Req3 = +</I>>>>><i> cowboy_req:set_resp_header(<<"Access-Control-Allow-Headers">>, +</I>>>>><i> <<"Content-Type, X-Requested-With, Origin, Method">>, Req2), +</I>>>>><i> cowboy_req:set_resp_header(<<"Access-Control-Allow-Origin">>, +</I>>>>><i> <<"*">>, Req3). +</I>>>>><i> +</I>>>>><i> I'm afraid I don't have any more info, but this issue is completely +</I>>>>><i> eluding me. +</I>>>>><i> +</I>>>>><i> Thanks, +</I>>>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>>>><i> +</I>>>><i> +</I>>><i> +</I>>><i> +</I>><i> +</I>><i> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000118.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000120.html">[99s-extend] 505 error +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#119">[ date ]</a> + <a href="thread.html#119">[ thread ]</a> + <a href="subject.html#119">[ subject ]</a> + <a href="author.html#119">[ 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/_build/static/archives/extend/2013-April/000120.html b/_build/static/archives/extend/2013-April/000120.html new file mode 100644 index 00000000..1c18db93 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000120.html @@ -0,0 +1,229 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] 505 error + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C51758D4B.1020501%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="000119.html"> + <LINK REL="Next" HREF="000121.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] 505 error</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20505%20error&In-Reply-To=%3C51758D4B.1020501%40ninenines.eu%3E" + TITLE="[99s-extend] 505 error">essen at ninenines.eu + </A><BR> + <I>Mon Apr 22 21:19:39 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000119.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000121.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#120">[ date ]</a> + <a href="thread.html#120">[ thread ]</a> + <a href="subject.html#120">[ subject ]</a> + <a href="author.html#120">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>I'm going to need the exact request line to make sense of it. +Something's missing in the parser I think, not sure what in your case +though. Feel free to private email it. + +On 04/22/2013 08:30 PM, Lee Sylvester wrote: +><i> Does this help? +</I>><i> +</I>><i> Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>><i> Request Method:OPTIONS +</I>><i> Status Code:505 HTTP Version Not Supported +</I>><i> +</I>><i> Request Headersview parsed +</I>><i> OPTIONS <A HREF="http://www.example.com">http://www.example.com</A> HTTP/1.1 +</I>><i> Host: www.example.com +</I>><i> Proxy-Connection: keep-alive +</I>><i> Access-Control-Request-Method: POST +</I>><i> Origin: <A HREF="http://localhost">http://localhost</A> +</I>><i> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31 +</I>><i> Access-Control-Request-Headers: origin, method, content-type +</I>><i> Accept: */* +</I>><i> Referer: <A HREF="http://localhost/p/">http://localhost/p/</A> +</I>><i> Accept-Encoding: gzip,deflate,sdch +</I>><i> Accept-Language: en-US,en;q=0.8 +</I>><i> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>><i> +</I>><i> Response Headersview parsed +</I>><i> HTTP/1.1 505 HTTP Version Not Supported +</I>><i> connection: close +</I>><i> server: Cowboy +</I>><i> date: Mon, 22 Apr 2013 17:42:39 GMT +</I>><i> content-length: 0 +</I>><i> +</I>><i> Thanks, +</I>><i> Lee +</I>><i> +</I>><i> +</I>><i> On 22 Apr 2013, at 16:55, "Brown, Kevin" <<A HREF="https://lists.ninenines.eu/listinfo/extend">Kevin.Brown at turner.com</A>> wrote: +</I>><i> +</I>>><i> You might see if "view source" (rather than the parsed view you sent) +</I>>><i> yields any clues. You'd like to see HTTP version being sent. +</I>>><i> +</I>>><i> +</I>>><i> On 4/22/13 10:40 AM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>>><i> +</I>>>><i> Well, the below is the sent and return headers on the failing machine. +</I>>>><i> On a succeeding machine, the headers are +</I>>>><i> +</I>>>><i> Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>>>><i> Request Method:OPTIONS +</I>>>><i> Status Code:200 OK +</I>>>><i> +</I>>>><i> Request Headersview source +</I>>>><i> Accept:*/* +</I>>>><i> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>>>><i> Accept-Encoding:gzip,deflate,sdch +</I>>>><i> Accept-Language:en-US,en;q=0.8 +</I>>>><i> Access-Control-Request-Headers:origin, method, content-type +</I>>>><i> Access-Control-Request-Method:POST +</I>>>><i> Connection:keep-alive +</I>>>><i> Host:www.example.com +</I>>>><i> Origin:<A HREF="http://www.test.com">http://www.test.com</A> +</I>>>><i> Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +</I>>>><i> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) +</I>>>><i> AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 +</I>>>><i> +</I>>>><i> Response Headersview source +</I>>>><i> Access-Control-Allow-Headers:Content-Type, X-Requested-With, Origin, +</I>>>><i> Method +</I>>>><i> Access-Control-Allow-Methods:GET, POST, OPTIONS +</I>>>><i> Access-Control-Allow-Origin:* +</I>>>><i> connection:keep-alive +</I>>>><i> content-length:68 +</I>>>><i> date:Mon, 22 Apr 2013 14:33:30 GMT +</I>>>><i> server:Cowboy +</I>>>><i> +</I>>>><i> As you can see, the header control and content isn't being sent back and +</I>>>><i> the connection is closed. +</I>>>><i> +</I>>>><i> Thanks, +</I>>>><i> Lee +</I>>>><i> +</I>>>><i> +</I>>>><i> +</I>>>><i> +</I>>>><i> On 22 Apr 2013, at 15:28, "Brown, Kevin" <<A HREF="https://lists.ninenines.eu/listinfo/extend">Kevin.Brown at turner.com</A>> wrote: +</I>>>><i> +</I>>>>><i> What is the exact http request sent on the failing and successful +</I>>>>><i> machines? How do the differ? +</I>>>>><i> +</I>>>>><i> Stack trace? +</I>>>>><i> +</I>>>>><i> On Apr 22, 2013, at 9:00 AM, "Lee Sylvester" <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> +</I>>>>><i> wrote: +</I>>>>><i> +</I>>>>>><i> Hi guys, +</I>>>>>><i> +</I>>>>>><i> So, I was getting a CORS issue when connecting to my Bullet impl, +</I>>>>>><i> which I have since fixed. I am now able to use these from many +</I>>>>>><i> machines from many locations. However, I have found some machines to +</I>>>>>><i> be getting a 505 error when making a POST request to the Cowboy +</I>>>>>><i> instance: +</I>>>>>><i> +</I>>>>>><i> Request URL:<A HREF="http://www.example.com">http://www.example.com</A> +</I>>>>>><i> Request Method:OPTIONS +</I>>>>>><i> Status Code:505 HTTP Version Not Supported +</I>>>>>><i> +</I>>>>>><i> Request Headersview source +</I>>>>>><i> Accept:*/* +</I>>>>>><i> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 +</I>>>>>><i> Accept-Encoding:gzip,deflate,sdch +</I>>>>>><i> Accept-Language:en-US,en;q=0.8 +</I>>>>>><i> Access-Control-Request-Headers:origin, method, content-type +</I>>>>>><i> Access-Control-Request-Method:POST +</I>>>>>><i> Connection:keep-alive +</I>>>>>><i> Host:www.example.com +</I>>>>>><i> Origin:<A HREF="http://www.test.com">http://www.test.com</A> +</I>>>>>><i> Referer:<A HREF="http://www.test.com/">http://www.test.com/</A> +</I>>>>>><i> User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 +</I>>>>>><i> (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31 +</I>>>>>><i> +</I>>>>>><i> Response Headersview source +</I>>>>>><i> connection:close +</I>>>>>><i> content-length:0 +</I>>>>>><i> date:Mon, 22 Apr 2013 12:22:50 GMT +</I>>>>>><i> server:Cowboy +</I>>>>>><i> +</I>>>>>><i> To get around the CORS issue, I set up an onrequest hook, which points +</I>>>>>><i> to the function: +</I>>>>>><i> +</I>>>>>><i> set_request_cors(Req) -> +</I>>>>>><i> Req2 = +</I>>>>>><i> cowboy_req:set_resp_header(<<"Access-Control-Allow-Methods">>, <<"GET, +</I>>>>>><i> POST, OPTIONS">>, Req), +</I>>>>>><i> Req3 = +</I>>>>>><i> cowboy_req:set_resp_header(<<"Access-Control-Allow-Headers">>, +</I>>>>>><i> <<"Content-Type, X-Requested-With, Origin, Method">>, Req2), +</I>>>>>><i> cowboy_req:set_resp_header(<<"Access-Control-Allow-Origin">>, +</I>>>>>><i> <<"*">>, Req3). +</I>>>>>><i> +</I>>>>>><i> I'm afraid I don't have any more info, but this issue is completely +</I>>>>>><i> eluding me. +</I>>>>>><i> +</I>>>>>><i> Thanks, +</I>>>>>><i> Lee +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>>>>><i> +</I>>>>><i> +</I>>>><i> +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>><i> +</I> + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000119.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000121.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#120">[ date ]</a> + <a href="thread.html#120">[ thread ]</a> + <a href="subject.html#120">[ subject ]</a> + <a href="author.html#120">[ 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/_build/static/archives/extend/2013-April/000121.html b/_build/static/archives/extend/2013-April/000121.html new file mode 100644 index 00000000..a1fc20ce --- /dev/null +++ b/_build/static/archives/extend/2013-April/000121.html @@ -0,0 +1,66 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] does cowboy support hot code reload/replace ? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20does%20cowboy%20support%20hot%20code%20reload/replace%20%3F&In-Reply-To=%3CCAN_mQBqbjr_JzSoL%3DYOzM8SaMbmvd%3D_OJ5FMg-DbYgKeYq6hBA%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="000120.html"> + <LINK REL="Next" HREF="000122.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] does cowboy support hot code reload/replace ?</H1> + <B>yongboy</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20does%20cowboy%20support%20hot%20code%20reload/replace%20%3F&In-Reply-To=%3CCAN_mQBqbjr_JzSoL%3DYOzM8SaMbmvd%3D_OJ5FMg-DbYgKeYq6hBA%40mail.gmail.com%3E" + TITLE="[99s-extend] does cowboy support hot code reload/replace ?">yongboy at gmail.com + </A><BR> + <I>Thu Apr 25 05:46:24 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000120.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000122.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#121">[ date ]</a> + <a href="thread.html#121">[ thread ]</a> + <a href="subject.html#121">[ subject ]</a> + <a href="author.html#121">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>You know, the OTP's code_change so heavy, sometimes, you just want to +debug, or change a little, does not want to rewrite the rel appup file. +Any help is appreciated, thanks. +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20130425/35ee7614/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130425/35ee7614/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000120.html">[99s-extend] 505 error +</A></li> + <LI>Next message: <A HREF="000122.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#121">[ date ]</a> + <a href="thread.html#121">[ thread ]</a> + <a href="subject.html#121">[ subject ]</a> + <a href="author.html#121">[ 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/_build/static/archives/extend/2013-April/000122.html b/_build/static/archives/extend/2013-April/000122.html new file mode 100644 index 00000000..1c5d02fb --- /dev/null +++ b/_build/static/archives/extend/2013-April/000122.html @@ -0,0 +1,76 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] does cowboy support hot code reload/replace ? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20does%20cowboy%20support%20hot%20code%20reload/replace%20%3F&In-Reply-To=%3C51791697.7030500%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="000121.html"> + <LINK REL="Next" HREF="000123.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] does cowboy support hot code reload/replace ?</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20does%20cowboy%20support%20hot%20code%20reload/replace%20%3F&In-Reply-To=%3C51791697.7030500%40ninenines.eu%3E" + TITLE="[99s-extend] does cowboy support hot code reload/replace ?">essen at ninenines.eu + </A><BR> + <I>Thu Apr 25 13:42:15 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000121.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI>Next message: <A HREF="000123.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#122">[ date ]</a> + <a href="thread.html#122">[ thread ]</a> + <a href="subject.html#122">[ subject ]</a> + <a href="author.html#122">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 04/25/2013 05:46 AM, yongboy wrote: +><i> You know, the OTP's code_change so heavy, sometimes, you just want to +</I>><i> debug, or change a little, does not want to rewrite the rel appup file. +</I>><i> Any help is appreciated, thanks. +</I> +At this time there is no code_change mechanism in Cowboy. Reloading a +module works, modifying the protocol options with +ranch:set_protocol_options can be used, but it doesn't change the +running processes. + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000121.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI>Next message: <A HREF="000123.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#122">[ date ]</a> + <a href="thread.html#122">[ thread ]</a> + <a href="subject.html#122">[ subject ]</a> + <a href="author.html#122">[ 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/_build/static/archives/extend/2013-April/000123.html b/_build/static/archives/extend/2013-April/000123.html new file mode 100644 index 00000000..1876b3f4 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000123.html @@ -0,0 +1,87 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] does cowboy support hot code reload/replace ? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20does%20cowboy%20support%20hot%20code%20reload/replace%20%3F&In-Reply-To=%3CCAN_mQBq4FEG66Ot2CpTLgChaaTMUW1vG0cjsZrEs-Rbms7zGuQ%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="000122.html"> + <LINK REL="Next" HREF="000124.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] does cowboy support hot code reload/replace ?</H1> + <B>yongboy</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20does%20cowboy%20support%20hot%20code%20reload/replace%20%3F&In-Reply-To=%3CCAN_mQBq4FEG66Ot2CpTLgChaaTMUW1vG0cjsZrEs-Rbms7zGuQ%40mail.gmail.com%3E" + TITLE="[99s-extend] does cowboy support hot code reload/replace ?">yongboy at gmail.com + </A><BR> + <I>Fri Apr 26 07:57:00 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000122.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI>Next message: <A HREF="000124.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#123">[ date ]</a> + <a href="thread.html#123">[ thread ]</a> + <a href="subject.html#123">[ subject ]</a> + <a href="author.html#123">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thanks very much ! +Maybe we can use the code:load_file() function I had just found it . + + +2013/4/25 Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>> + +><i> On 04/25/2013 05:46 AM, yongboy wrote: +</I>><i> +</I>>><i> You know, the OTP's code_change so heavy, sometimes, you just want to +</I>>><i> debug, or change a little, does not want to rewrite the rel appup file. +</I>>><i> Any help is appreciated, thanks. +</I>>><i> +</I>><i> +</I>><i> At this time there is no code_change mechanism in Cowboy. Reloading a +</I>><i> module works, modifying the protocol options with +</I>><i> ranch:set_protocol_options can be used, but it doesn't change the running +</I>><i> processes. +</I>><i> +</I>><i> -- +</I>><i> Loďc Hoguin +</I>><i> Erlang Cowboy +</I>><i> Nine Nines +</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/20130426/09f3ed34/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130426/09f3ed34/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000122.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI>Next message: <A HREF="000124.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#123">[ date ]</a> + <a href="thread.html#123">[ thread ]</a> + <a href="subject.html#123">[ subject ]</a> + <a href="author.html#123">[ 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/_build/static/archives/extend/2013-April/000124.html b/_build/static/archives/extend/2013-April/000124.html new file mode 100644 index 00000000..08b363e5 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000124.html @@ -0,0 +1,122 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy how to ruduce the memory usage per long-hold connection + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20how%20to%20ruduce%20the%20memory%20usage%20per%20long-hold%0A%09connection&In-Reply-To=%3CCAN_mQBobPN0zdpqJ3WtGKJaRMNiutvurgJfncMCqM3qtUHTm1g%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="000123.html"> + <LINK REL="Next" HREF="000125.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy how to ruduce the memory usage per long-hold connection</H1> + <B>yongboy</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20how%20to%20ruduce%20the%20memory%20usage%20per%20long-hold%0A%09connection&In-Reply-To=%3CCAN_mQBobPN0zdpqJ3WtGKJaRMNiutvurgJfncMCqM3qtUHTm1g%40mail.gmail.com%3E" + TITLE="[99s-extend] cowboy how to ruduce the memory usage per long-hold connection">yongboy at gmail.com + </A><BR> + <I>Fri Apr 26 08:11:56 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000123.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI>Next message: <A HREF="000125.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#124">[ date ]</a> + <a href="thread.html#124">[ thread ]</a> + <a href="subject.html#124">[ subject ]</a> + <a href="author.html#124">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>I have tested one long-hold webapp, when 512000 user connected, the app +used +6801M memory, 6801M*1024K / 512000 = 13.6K/Connection. + +Does anyone give me some advice on how to reduce the memory usage per one +connection, thanks very much ! + +Here is the code snippet: + +start(_Type, _Args) -> + Dispatch = cowboy_router:compile([ + {'_', [{'_', htmlfile_handler, []}]} + ]), + cowboy:start_http(my_http_listener, 100, + [{port, 8000}, {max_connections, infinity}], + [{env, [{dispatch, Dispatch}]}] + ), + count_server:start(), + htmlfilesimple_sup:start_link(). + +...... + +-module(htmlfile_handler). +-behaviour(cowboy_loop_handler). +-export([init/3, info/3, terminate/3]). +-define(HEARBEAT_TIMEOUT, 20*1000). +-record(status, {count=0}). + +init(_Any, Req, State) -> + NowCount = count_server:welcome(), + io:format("online user ~p :))~n", [NowCount]), + + output_first(Req), + Req2 = cowboy_req:compact(Req), + {loop, Req2, State, hibernate}. + +%% POST/Short Request +info(_Any, Req, State) -> + {loop, Req, State, hibernate}. + +output_first(Req) -> + {ok, Reply} = cowboy_req:chunked_reply(200, [{<<"Content-Type">>, +<<"text/html; charset=utf-8">>}, + +{<<"Connection">>, <<"keep-alive">>}], Req), + cowboy_req:chunk(<<"<html><body><script>var _ = function (msg) { +parent.s._(msg, document); +};</script> +">>, + Reply), + cowboy_req:chunk(gen_output("1::"), Reply). + +gen_output(String) -> + DescList = io_lib:format("<script>_('~s');</script>", [String]), + list_to_binary(DescList). + +terminate(Reason, _Req, _State) -> + NowCount = count_server:bye(), + io:format("offline user ~p :(( ~n", [NowCount]). +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20130426/9d234e27/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130426/9d234e27/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000123.html">[99s-extend] does cowboy support hot code reload/replace ? +</A></li> + <LI>Next message: <A HREF="000125.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#124">[ date ]</a> + <a href="thread.html#124">[ thread ]</a> + <a href="subject.html#124">[ subject ]</a> + <a href="author.html#124">[ 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/_build/static/archives/extend/2013-April/000125.html b/_build/static/archives/extend/2013-April/000125.html new file mode 100644 index 00000000..6fd69519 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000125.html @@ -0,0 +1,140 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy how to ruduce the memory usage per long-hold connection + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20how%20to%20ruduce%20the%20memory%20usage%20per%0A%09long-hold%20connection&In-Reply-To=%3CCAJ0zLRPcYmH1OXeiw2aZHLtoqqdW%3Ddu0rhonF53xdCbMUmnCLw%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="000124.html"> + <LINK REL="Next" HREF="000126.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy how to ruduce the memory usage per long-hold connection</H1> + <B>rambocoder</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20how%20to%20ruduce%20the%20memory%20usage%20per%0A%09long-hold%20connection&In-Reply-To=%3CCAJ0zLRPcYmH1OXeiw2aZHLtoqqdW%3Ddu0rhonF53xdCbMUmnCLw%40mail.gmail.com%3E" + TITLE="[99s-extend] cowboy how to ruduce the memory usage per long-hold connection">erlang at rambocoder.com + </A><BR> + <I>Fri Apr 26 15:11:53 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000124.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A></li> + <LI>Next message: <A HREF="000126.html">[99s-extend] [ANN] Cowboy 0.8.4 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#125">[ date ]</a> + <a href="thread.html#125">[ thread ]</a> + <a href="subject.html#125">[ subject ]</a> + <a href="author.html#125">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Is 13.6K/connection considered a lot? Once you start doing SSL, each +connection will be about 80K, IMHO the most important factor for huge +ammount of COMET users is latency, which Cowboy and Erlang do great. + +-rambocoder + +On Fri, Apr 26, 2013 at 2:11 AM, yongboy <<A HREF="https://lists.ninenines.eu/listinfo/extend">yongboy at gmail.com</A>> wrote: + +><i> I have tested one long-hold webapp, when 512000 user connected, the app +</I>><i> used +</I>><i> 6801M memory, 6801M*1024K / 512000 = 13.6K/Connection. +</I>><i> +</I>><i> Does anyone give me some advice on how to reduce the memory usage per one +</I>><i> connection, thanks very much ! +</I>><i> +</I>><i> Here is the code snippet: +</I>><i> +</I>><i> start(_Type, _Args) -> +</I>><i> Dispatch = cowboy_router:compile([ +</I>><i> {'_', [{'_', htmlfile_handler, []}]} +</I>><i> ]), +</I>><i> cowboy:start_http(my_http_listener, 100, +</I>><i> [{port, 8000}, {max_connections, infinity}], +</I>><i> [{env, [{dispatch, Dispatch}]}] +</I>><i> ), +</I>><i> count_server:start(), +</I>><i> htmlfilesimple_sup:start_link(). +</I>><i> +</I>><i> ...... +</I>><i> +</I>><i> -module(htmlfile_handler). +</I>><i> -behaviour(cowboy_loop_handler). +</I>><i> -export([init/3, info/3, terminate/3]). +</I>><i> -define(HEARBEAT_TIMEOUT, 20*1000). +</I>><i> -record(status, {count=0}). +</I>><i> +</I>><i> init(_Any, Req, State) -> +</I>><i> NowCount = count_server:welcome(), +</I>><i> io:format("online user ~p :))~n", [NowCount]), +</I>><i> +</I>><i> output_first(Req), +</I>><i> Req2 = cowboy_req:compact(Req), +</I>><i> {loop, Req2, State, hibernate}. +</I>><i> +</I>><i> %% POST/Short Request +</I>><i> info(_Any, Req, State) -> +</I>><i> {loop, Req, State, hibernate}. +</I>><i> +</I>><i> output_first(Req) -> +</I>><i> {ok, Reply} = cowboy_req:chunked_reply(200, [{<<"Content-Type">>, +</I>><i> <<"text/html; charset=utf-8">>}, +</I>><i> +</I>><i> {<<"Connection">>, <<"keep-alive">>}], Req), +</I>><i> cowboy_req:chunk(<<"<html><body><script>var _ = function (msg) { +</I>><i> parent.s._(msg, document); +</I>><i> };</script> +</I>><i> ">>, +</I>><i> Reply), +</I>><i> cowboy_req:chunk(gen_output("1::"), Reply). +</I>><i> +</I>><i> gen_output(String) -> +</I>><i> DescList = io_lib:format("<script>_('~s');</script>", [String]), +</I>><i> list_to_binary(DescList). +</I>><i> +</I>><i> terminate(Reason, _Req, _State) -> +</I>><i> NowCount = count_server:bye(), +</I>><i> io:format("offline user ~p :(( ~n", [NowCount]). +</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="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/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/20130426/b1e8ae7a/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130426/b1e8ae7a/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000124.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A></li> + <LI>Next message: <A HREF="000126.html">[99s-extend] [ANN] Cowboy 0.8.4 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#125">[ date ]</a> + <a href="thread.html#125">[ thread ]</a> + <a href="subject.html#125">[ subject ]</a> + <a href="author.html#125">[ 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/_build/static/archives/extend/2013-April/000126.html b/_build/static/archives/extend/2013-April/000126.html new file mode 100644 index 00000000..093d494d --- /dev/null +++ b/_build/static/archives/extend/2013-April/000126.html @@ -0,0 +1,90 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] [ANN] Cowboy 0.8.4 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20%5BANN%5D%20Cowboy%200.8.4&In-Reply-To=%3C517A9B7C.8090706%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="000125.html"> + <LINK REL="Next" HREF="000127.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] [ANN] Cowboy 0.8.4</H1> + <B>Loïc Hoguin</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20%5BANN%5D%20Cowboy%200.8.4&In-Reply-To=%3C517A9B7C.8090706%40ninenines.eu%3E" + TITLE="[99s-extend] [ANN] Cowboy 0.8.4">essen at ninenines.eu + </A><BR> + <I>Fri Apr 26 17:21:32 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000125.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A></li> + <LI>Next message: <A HREF="000127.html">[99s-extend] cowboy websocket and wamp +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#126">[ date ]</a> + <a href="thread.html#126">[ thread ]</a> + <a href="subject.html#126">[ subject ]</a> + <a href="author.html#126">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello, + +Cowboy 0.8.4 has been released! + +This release features a tentatively stable API. This means that the +complete API defined in this release should not change anymore. The API +will be augmented with many features and functions of course, but +existing code should not break anymore. Changes will only be considered +if a feature causes bugs or too much confusion to the majority of users. + +This release includes all the remaining changes that had to be done to +REST, which is now no longer experimental and has documentation that you +can find here: + + <A HREF="http://ninenines.eu/docs/en/cowboy/HEAD/guide/rest_handlers">http://ninenines.eu/docs/en/cowboy/HEAD/guide/rest_handlers</A> + +Diagrams and their explanations will be added to the documentation in +the next few days. + +The full changelog for this release can be found here: +<A HREF="https://github.com/extend/cowboy/commit/46b2ea0aaa7fe891bfdf3f8a0c47357393e72cf6">https://github.com/extend/cowboy/commit/46b2ea0aaa7fe891bfdf3f8a0c47357393e72cf6</A> + +Enjoy! + +-- +Loïc Hoguin +Erlang Cowboy +Nine Nines +<A HREF="http://ninenines.eu">http://ninenines.eu</A> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000125.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A></li> + <LI>Next message: <A HREF="000127.html">[99s-extend] cowboy websocket and wamp +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#126">[ date ]</a> + <a href="thread.html#126">[ thread ]</a> + <a href="subject.html#126">[ subject ]</a> + <a href="author.html#126">[ 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/_build/static/archives/extend/2013-April/000127.html b/_build/static/archives/extend/2013-April/000127.html new file mode 100644 index 00000000..cc767686 --- /dev/null +++ b/_build/static/archives/extend/2013-April/000127.html @@ -0,0 +1,75 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] cowboy websocket and wamp + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20websocket%20and%20wamp&In-Reply-To=%3CCAAh%2BK4zu6f1CM1Dij7XsnUCLXXqaS3E6ZugABuaiST99Pz%2BKnA%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="000126.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] cowboy websocket and wamp</H1> + <B>Gregory de Souza</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20cowboy%20websocket%20and%20wamp&In-Reply-To=%3CCAAh%2BK4zu6f1CM1Dij7XsnUCLXXqaS3E6ZugABuaiST99Pz%2BKnA%40mail.gmail.com%3E" + TITLE="[99s-extend] cowboy websocket and wamp">gdesouza at gmail.com + </A><BR> + <I>Tue Apr 30 20:59:21 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000126.html">[99s-extend] [ANN] Cowboy 0.8.4 +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#127">[ date ]</a> + <a href="thread.html#127">[ thread ]</a> + <a href="subject.html#127">[ subject ]</a> + <a href="author.html#127">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, +I'm new to the community and am exploring cowboy for a project. + +Can anyone offer guidance/links on how to use cowboy's websocket support +with WAMP (<A HREF="http://wamp.ws/">http://wamp.ws/</A>)? +The cowboy docs mention bullet <<A HREF="https://github.com/extend/bullet?source=cr">https://github.com/extend/bullet?source=cr</A>> as +a convenient client/server lib (with an AJAX fallback) which is great, but +I'd like to use WAMP's RPC and PubSub so I'm unsure how to proceed. + +Any tips would be appreciated! + +Thanks in advance +-- +Gregory | @gdesouza <<A HREF="http://twitter.com/gdesouza">http://twitter.com/gdesouza</A>> | <A HREF="http://blog.gdesouza.me">http://blog.gdesouza.me</A> +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20130430/c86f8fdb/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20130430/c86f8fdb/attachment.html</A>> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000126.html">[99s-extend] [ANN] Cowboy 0.8.4 +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#127">[ date ]</a> + <a href="thread.html#127">[ thread ]</a> + <a href="subject.html#127">[ subject ]</a> + <a href="author.html#127">[ 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/_build/static/archives/extend/2013-April/author.html b/_build/static/archives/extend/2013-April/author.html new file mode 100644 index 00000000..f8edc33c --- /dev/null +++ b/_build/static/archives/extend/2013-April/author.html @@ -0,0 +1,322 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <title>The Extend April 2013 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>April 2013 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>Tue Apr 2 19:23:28 CEST 2013</i><br> + <b>Ending:</b> <i>Tue Apr 30 20:59:21 CEST 2013</i><br> + <b>Messages:</b> 55<p> + <ul> + +<LI><A HREF="000104.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="104"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000106.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="106"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000115.html">[99s-extend] 505 error +</A><A NAME="115"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000118.html">[99s-extend] 505 error +</A><A NAME="118"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000107.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="107"> </A> +<I>Eduardo Gurgel +</I> + +<LI><A HREF="000073.html">[99s-extend] [ANN] Ranch 0.8.0 +</A><A NAME="73"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000074.html">[99s-extend] [ANN] Cowboy 0.8.3 +</A><A NAME="74"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000079.html">[99s-extend] Bullet connection +</A><A NAME="79"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000082.html">[99s-extend] Problems with Bullet +</A><A NAME="82"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000088.html">[99s-extend] Heartbeat? +</A><A NAME="88"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000089.html">[99s-extend] cowboy and chromium +</A><A NAME="89"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000091.html">[99s-extend] cowboy and chromium +</A><A NAME="91"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000094.html">[99s-extend] cowboy and chromium +</A><A NAME="94"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000096.html">[99s-extend] cowboy and chromium +</A><A NAME="96"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000105.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="105"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000109.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="109"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000111.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="111"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000117.html">[99s-extend] 505 error +</A><A NAME="117"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000120.html">[99s-extend] 505 error +</A><A NAME="120"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000122.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="122"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000126.html">[99s-extend] [ANN] Cowboy 0.8.4 +</A><A NAME="126"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000087.html">[99s-extend] cowboy and chromium +</A><A NAME="87"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000090.html">[99s-extend] cowboy and chromium +</A><A NAME="90"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000093.html">[99s-extend] cowboy and chromium +</A><A NAME="93"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000095.html">[99s-extend] cowboy and chromium +</A><A NAME="95"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000097.html">[99s-extend] cowboy and chromium +</A><A NAME="97"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000099.html">[99s-extend] Distributed model? +</A><A NAME="99"> </A> +<I>Jeremy Ong +</I> + +<LI><A HREF="000101.html">[99s-extend] Distributed model? +</A><A NAME="101"> </A> +<I>Jeremy Ong +</I> + +<LI><A HREF="000076.html">[99s-extend] Response headers +</A><A NAME="76"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000083.html">[99s-extend] Problems with Bullet +</A><A NAME="83"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000084.html">[99s-extend] Problems with Bullet +</A><A NAME="84"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000113.html">[99s-extend] Cowboy CORS +</A><A NAME="113"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000127.html">[99s-extend] cowboy websocket and wamp +</A><A NAME="127"> </A> +<I>Gregory de Souza +</I> + +<LI><A HREF="000075.html">[99s-extend] Response headers +</A><A NAME="75"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000077.html">[99s-extend] Response headers +</A><A NAME="77"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000078.html">[99s-extend] Bullet connection +</A><A NAME="78"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000080.html">[99s-extend] Bullet connection +</A><A NAME="80"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000081.html">[99s-extend] Problems with Bullet +</A><A NAME="81"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000085.html">[99s-extend] Problems with Bullet +</A><A NAME="85"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000086.html">[99s-extend] Heartbeat? +</A><A NAME="86"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000092.html">[99s-extend] Heartbeat? +</A><A NAME="92"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000098.html">[99s-extend] Distributed model? +</A><A NAME="98"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000100.html">[99s-extend] Distributed model? +</A><A NAME="100"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000102.html">[99s-extend] Distributed model? +</A><A NAME="102"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000103.html">[99s-extend] Distributed model? +</A><A NAME="103"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000112.html">[99s-extend] Cowboy CORS +</A><A NAME="112"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000114.html">[99s-extend] 505 error +</A><A NAME="114"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000116.html">[99s-extend] 505 error +</A><A NAME="116"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000119.html">[99s-extend] 505 error +</A><A NAME="119"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000108.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="108"> </A> +<I>rambocoder +</I> + +<LI><A HREF="000110.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="110"> </A> +<I>rambocoder +</I> + +<LI><A HREF="000125.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A><A NAME="125"> </A> +<I>rambocoder +</I> + +<LI><A HREF="000121.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="121"> </A> +<I>yongboy +</I> + +<LI><A HREF="000123.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="123"> </A> +<I>yongboy +</I> + +<LI><A HREF="000124.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A><A NAME="124"> </A> +<I>yongboy +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Tue Apr 30 20:59:21 CEST 2013</i><br> + <b>Archived on:</b> <i>Wed May 28 18:41:43 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/_build/static/archives/extend/2013-April/date.html b/_build/static/archives/extend/2013-April/date.html new file mode 100644 index 00000000..a3b39452 --- /dev/null +++ b/_build/static/archives/extend/2013-April/date.html @@ -0,0 +1,322 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <title>The Extend April 2013 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>April 2013 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>Tue Apr 2 19:23:28 CEST 2013</i><br> + <b>Ending:</b> <i>Tue Apr 30 20:59:21 CEST 2013</i><br> + <b>Messages:</b> 55<p> + <ul> + +<LI><A HREF="000073.html">[99s-extend] [ANN] Ranch 0.8.0 +</A><A NAME="73"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000074.html">[99s-extend] [ANN] Cowboy 0.8.3 +</A><A NAME="74"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000075.html">[99s-extend] Response headers +</A><A NAME="75"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000076.html">[99s-extend] Response headers +</A><A NAME="76"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000077.html">[99s-extend] Response headers +</A><A NAME="77"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000078.html">[99s-extend] Bullet connection +</A><A NAME="78"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000079.html">[99s-extend] Bullet connection +</A><A NAME="79"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000080.html">[99s-extend] Bullet connection +</A><A NAME="80"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000081.html">[99s-extend] Problems with Bullet +</A><A NAME="81"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000082.html">[99s-extend] Problems with Bullet +</A><A NAME="82"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000083.html">[99s-extend] Problems with Bullet +</A><A NAME="83"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000084.html">[99s-extend] Problems with Bullet +</A><A NAME="84"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000085.html">[99s-extend] Problems with Bullet +</A><A NAME="85"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000086.html">[99s-extend] Heartbeat? +</A><A NAME="86"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000087.html">[99s-extend] cowboy and chromium +</A><A NAME="87"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000088.html">[99s-extend] Heartbeat? +</A><A NAME="88"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000089.html">[99s-extend] cowboy and chromium +</A><A NAME="89"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000090.html">[99s-extend] cowboy and chromium +</A><A NAME="90"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000091.html">[99s-extend] cowboy and chromium +</A><A NAME="91"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000092.html">[99s-extend] Heartbeat? +</A><A NAME="92"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000093.html">[99s-extend] cowboy and chromium +</A><A NAME="93"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000094.html">[99s-extend] cowboy and chromium +</A><A NAME="94"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000095.html">[99s-extend] cowboy and chromium +</A><A NAME="95"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000096.html">[99s-extend] cowboy and chromium +</A><A NAME="96"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000097.html">[99s-extend] cowboy and chromium +</A><A NAME="97"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000098.html">[99s-extend] Distributed model? +</A><A NAME="98"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000099.html">[99s-extend] Distributed model? +</A><A NAME="99"> </A> +<I>Jeremy Ong +</I> + +<LI><A HREF="000100.html">[99s-extend] Distributed model? +</A><A NAME="100"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000101.html">[99s-extend] Distributed model? +</A><A NAME="101"> </A> +<I>Jeremy Ong +</I> + +<LI><A HREF="000102.html">[99s-extend] Distributed model? +</A><A NAME="102"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000103.html">[99s-extend] Distributed model? +</A><A NAME="103"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000104.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="104"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000105.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="105"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000106.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="106"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000107.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="107"> </A> +<I>Eduardo Gurgel +</I> + +<LI><A HREF="000108.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="108"> </A> +<I>rambocoder +</I> + +<LI><A HREF="000109.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="109"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000110.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="110"> </A> +<I>rambocoder +</I> + +<LI><A HREF="000111.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="111"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000112.html">[99s-extend] Cowboy CORS +</A><A NAME="112"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000113.html">[99s-extend] Cowboy CORS +</A><A NAME="113"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000114.html">[99s-extend] 505 error +</A><A NAME="114"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000115.html">[99s-extend] 505 error +</A><A NAME="115"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000116.html">[99s-extend] 505 error +</A><A NAME="116"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000117.html">[99s-extend] 505 error +</A><A NAME="117"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000118.html">[99s-extend] 505 error +</A><A NAME="118"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000119.html">[99s-extend] 505 error +</A><A NAME="119"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000120.html">[99s-extend] 505 error +</A><A NAME="120"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000121.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="121"> </A> +<I>yongboy +</I> + +<LI><A HREF="000122.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="122"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000123.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="123"> </A> +<I>yongboy +</I> + +<LI><A HREF="000124.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A><A NAME="124"> </A> +<I>yongboy +</I> + +<LI><A HREF="000125.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A><A NAME="125"> </A> +<I>rambocoder +</I> + +<LI><A HREF="000126.html">[99s-extend] [ANN] Cowboy 0.8.4 +</A><A NAME="126"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000127.html">[99s-extend] cowboy websocket and wamp +</A><A NAME="127"> </A> +<I>Gregory de Souza +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Tue Apr 30 20:59:21 CEST 2013</i><br> + <b>Archived on:</b> <i>Wed May 28 18:41:43 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/_build/static/archives/extend/2013-April/index.html b/_build/static/archives/extend/2013-April/index.html new file mode 120000 index 00000000..db4b46f7 --- /dev/null +++ b/_build/static/archives/extend/2013-April/index.html @@ -0,0 +1 @@ +thread.html
\ No newline at end of file diff --git a/_build/static/archives/extend/2013-April/subject.html b/_build/static/archives/extend/2013-April/subject.html new file mode 100644 index 00000000..741c7962 --- /dev/null +++ b/_build/static/archives/extend/2013-April/subject.html @@ -0,0 +1,322 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <title>The Extend April 2013 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>April 2013 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>Tue Apr 2 19:23:28 CEST 2013</i><br> + <b>Ending:</b> <i>Tue Apr 30 20:59:21 CEST 2013</i><br> + <b>Messages:</b> 55<p> + <ul> + +<LI><A HREF="000114.html">[99s-extend] 505 error +</A><A NAME="114"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000115.html">[99s-extend] 505 error +</A><A NAME="115"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000116.html">[99s-extend] 505 error +</A><A NAME="116"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000117.html">[99s-extend] 505 error +</A><A NAME="117"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000118.html">[99s-extend] 505 error +</A><A NAME="118"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000119.html">[99s-extend] 505 error +</A><A NAME="119"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000120.html">[99s-extend] 505 error +</A><A NAME="120"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000074.html">[99s-extend] [ANN] Cowboy 0.8.3 +</A><A NAME="74"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000126.html">[99s-extend] [ANN] Cowboy 0.8.4 +</A><A NAME="126"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000073.html">[99s-extend] [ANN] Ranch 0.8.0 +</A><A NAME="73"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000078.html">[99s-extend] Bullet connection +</A><A NAME="78"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000079.html">[99s-extend] Bullet connection +</A><A NAME="79"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000080.html">[99s-extend] Bullet connection +</A><A NAME="80"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000087.html">[99s-extend] cowboy and chromium +</A><A NAME="87"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000089.html">[99s-extend] cowboy and chromium +</A><A NAME="89"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000090.html">[99s-extend] cowboy and chromium +</A><A NAME="90"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000091.html">[99s-extend] cowboy and chromium +</A><A NAME="91"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000093.html">[99s-extend] cowboy and chromium +</A><A NAME="93"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000094.html">[99s-extend] cowboy and chromium +</A><A NAME="94"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000095.html">[99s-extend] cowboy and chromium +</A><A NAME="95"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000096.html">[99s-extend] cowboy and chromium +</A><A NAME="96"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000097.html">[99s-extend] cowboy and chromium +</A><A NAME="97"> </A> +<I>Sasa Juric +</I> + +<LI><A HREF="000112.html">[99s-extend] Cowboy CORS +</A><A NAME="112"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000113.html">[99s-extend] Cowboy CORS +</A><A NAME="113"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000124.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A><A NAME="124"> </A> +<I>yongboy +</I> + +<LI><A HREF="000125.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A><A NAME="125"> </A> +<I>rambocoder +</I> + +<LI><A HREF="000127.html">[99s-extend] cowboy websocket and wamp +</A><A NAME="127"> </A> +<I>Gregory de Souza +</I> + +<LI><A HREF="000098.html">[99s-extend] Distributed model? +</A><A NAME="98"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000099.html">[99s-extend] Distributed model? +</A><A NAME="99"> </A> +<I>Jeremy Ong +</I> + +<LI><A HREF="000100.html">[99s-extend] Distributed model? +</A><A NAME="100"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000101.html">[99s-extend] Distributed model? +</A><A NAME="101"> </A> +<I>Jeremy Ong +</I> + +<LI><A HREF="000102.html">[99s-extend] Distributed model? +</A><A NAME="102"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000103.html">[99s-extend] Distributed model? +</A><A NAME="103"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000121.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="121"> </A> +<I>yongboy +</I> + +<LI><A HREF="000122.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="122"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000123.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="123"> </A> +<I>yongboy +</I> + +<LI><A HREF="000086.html">[99s-extend] Heartbeat? +</A><A NAME="86"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000088.html">[99s-extend] Heartbeat? +</A><A NAME="88"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000092.html">[99s-extend] Heartbeat? +</A><A NAME="92"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000104.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="104"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000105.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="105"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000106.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="106"> </A> +<I>Brown, Kevin +</I> + +<LI><A HREF="000107.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="107"> </A> +<I>Eduardo Gurgel +</I> + +<LI><A HREF="000081.html">[99s-extend] Problems with Bullet +</A><A NAME="81"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000082.html">[99s-extend] Problems with Bullet +</A><A NAME="82"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000083.html">[99s-extend] Problems with Bullet +</A><A NAME="83"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000084.html">[99s-extend] Problems with Bullet +</A><A NAME="84"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000085.html">[99s-extend] Problems with Bullet +</A><A NAME="85"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000108.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="108"> </A> +<I>rambocoder +</I> + +<LI><A HREF="000109.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="109"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000110.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="110"> </A> +<I>rambocoder +</I> + +<LI><A HREF="000111.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="111"> </A> +<I>Loïc Hoguin +</I> + +<LI><A HREF="000075.html">[99s-extend] Response headers +</A><A NAME="75"> </A> +<I>Lee Sylvester +</I> + +<LI><A HREF="000076.html">[99s-extend] Response headers +</A><A NAME="76"> </A> +<I>Phillips, Christopher +</I> + +<LI><A HREF="000077.html">[99s-extend] Response headers +</A><A NAME="77"> </A> +<I>Lee Sylvester +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Tue Apr 30 20:59:21 CEST 2013</i><br> + <b>Archived on:</b> <i>Wed May 28 18:41:43 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/_build/static/archives/extend/2013-April/thread.html b/_build/static/archives/extend/2013-April/thread.html new file mode 100644 index 00000000..eafeca8a --- /dev/null +++ b/_build/static/archives/extend/2013-April/thread.html @@ -0,0 +1,431 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <title>The Extend April 2013 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>April 2013 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>Tue Apr 2 19:23:28 CEST 2013</i><br> + <b>Ending:</b> <i>Tue Apr 30 20:59:21 CEST 2013</i><br> + <b>Messages:</b> 55<p> + <ul> + +<!--0 01364923408.73- --> +<LI><A HREF="000073.html">[99s-extend] [ANN] Ranch 0.8.0 +</A><A NAME="73"> </A> +<I>Loïc Hoguin +</I> + +<!--0 01365002476.74- --> +<LI><A HREF="000074.html">[99s-extend] [ANN] Cowboy 0.8.3 +</A><A NAME="74"> </A> +<I>Loïc Hoguin +</I> + +<!--0 01365017600.75- --> +<LI><A HREF="000075.html">[99s-extend] Response headers +</A><A NAME="75"> </A> +<I>Lee Sylvester +</I> + +<UL> +<!--1 01365017600.75-01365021336.76- --> +<LI><A HREF="000076.html">[99s-extend] Response headers +</A><A NAME="76"> </A> +<I>Phillips, Christopher +</I> + +<UL> +<!--2 01365017600.75-01365021336.76-01365064687.77- --> +<LI><A HREF="000077.html">[99s-extend] Response headers +</A><A NAME="77"> </A> +<I>Lee Sylvester +</I> + +</UL> +</UL> +<!--0 01365106674.78- --> +<LI><A HREF="000078.html">[99s-extend] Bullet connection +</A><A NAME="78"> </A> +<I>Lee Sylvester +</I> + +<UL> +<!--1 01365106674.78-01365107972.79- --> +<LI><A HREF="000079.html">[99s-extend] Bullet connection +</A><A NAME="79"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01365106674.78-01365107972.79-01365108894.80- --> +<LI><A HREF="000080.html">[99s-extend] Bullet connection +</A><A NAME="80"> </A> +<I>Lee Sylvester +</I> + +</UL> +</UL> +<!--0 01365429218.81- --> +<LI><A HREF="000081.html">[99s-extend] Problems with Bullet +</A><A NAME="81"> </A> +<I>Lee Sylvester +</I> + +<UL> +<!--1 01365429218.81-01365430111.82- --> +<LI><A HREF="000082.html">[99s-extend] Problems with Bullet +</A><A NAME="82"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01365429218.81-01365430111.82-01365430707.84- --> +<LI><A HREF="000084.html">[99s-extend] Problems with Bullet +</A><A NAME="84"> </A> +<I>Phillips, Christopher +</I> + +<UL> +<!--3 01365429218.81-01365430111.82-01365430707.84-01365430913.85- --> +<LI><A HREF="000085.html">[99s-extend] Problems with Bullet +</A><A NAME="85"> </A> +<I>Lee Sylvester +</I> + +</UL> +</UL> +<!--1 01365429218.81-01365430304.83- --> +<LI><A HREF="000083.html">[99s-extend] Problems with Bullet +</A><A NAME="83"> </A> +<I>Phillips, Christopher +</I> + +</UL> +<!--0 01365594465.86- --> +<LI><A HREF="000086.html">[99s-extend] Heartbeat? +</A><A NAME="86"> </A> +<I>Lee Sylvester +</I> + +<UL> +<!--1 01365594465.86-01365604706.88- --> +<LI><A HREF="000088.html">[99s-extend] Heartbeat? +</A><A NAME="88"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01365594465.86-01365604706.88-01365605604.92- --> +<LI><A HREF="000092.html">[99s-extend] Heartbeat? +</A><A NAME="92"> </A> +<I>Lee Sylvester +</I> + +</UL> +</UL> +<!--0 01365595247.87- --> +<LI><A HREF="000087.html">[99s-extend] cowboy and chromium +</A><A NAME="87"> </A> +<I>Sasa Juric +</I> + +<UL> +<!--1 01365595247.87-01365604881.89- --> +<LI><A HREF="000089.html">[99s-extend] cowboy and chromium +</A><A NAME="89"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01365595247.87-01365604881.89-01365605431.90- --> +<LI><A HREF="000090.html">[99s-extend] cowboy and chromium +</A><A NAME="90"> </A> +<I>Sasa Juric +</I> + +<UL> +<!--3 01365595247.87-01365604881.89-01365605431.90-01365605510.91- --> +<LI><A HREF="000091.html">[99s-extend] cowboy and chromium +</A><A NAME="91"> </A> +<I>Loïc Hoguin +</I> + +<!--3 01365595247.87-01365604881.89-01365605431.90-01365605510.91-01365605768.93- --> +<LI><A HREF="000093.html">[99s-extend] cowboy and chromium +</A><A NAME="93"> </A> +<I>Sasa Juric +</I> + +<!--3 01365595247.87-01365604881.89-01365605431.90-01365605510.91-01365605768.93-01365606074.94- --> +<LI><A HREF="000094.html">[99s-extend] cowboy and chromium +</A><A NAME="94"> </A> +<I>Loïc Hoguin +</I> + +<!--3 01365595247.87-01365604881.89-01365605431.90-01365605510.91-01365605768.93-01365606074.94-01365606351.95- --> +<LI><A HREF="000095.html">[99s-extend] cowboy and chromium +</A><A NAME="95"> </A> +<I>Sasa Juric +</I> + +<!--3 01365595247.87-01365604881.89-01365605431.90-01365605510.91-01365605768.93-01365606074.94-01365606351.95-01365606438.96- --> +<LI><A HREF="000096.html">[99s-extend] cowboy and chromium +</A><A NAME="96"> </A> +<I>Loïc Hoguin +</I> + +<!--3 01365595247.87-01365604881.89-01365605431.90-01365605510.91-01365605768.93-01365606074.94-01365606351.95-01365606438.96-01365606717.97- --> +<LI><A HREF="000097.html">[99s-extend] cowboy and chromium +</A><A NAME="97"> </A> +<I>Sasa Juric +</I> + +</UL> +</UL> +</UL> +<!--0 01365659472.98- --> +<LI><A HREF="000098.html">[99s-extend] Distributed model? +</A><A NAME="98"> </A> +<I>Lee Sylvester +</I> + +<UL> +<!--1 01365659472.98-01365661756.99- --> +<LI><A HREF="000099.html">[99s-extend] Distributed model? +</A><A NAME="99"> </A> +<I>Jeremy Ong +</I> + +<UL> +<!--2 01365659472.98-01365661756.99-01365662958.100- --> +<LI><A HREF="000100.html">[99s-extend] Distributed model? +</A><A NAME="100"> </A> +<I>Lee Sylvester +</I> + +<UL> +<!--3 01365659472.98-01365661756.99-01365662958.100-01365663844.101- --> +<LI><A HREF="000101.html">[99s-extend] Distributed model? +</A><A NAME="101"> </A> +<I>Jeremy Ong +</I> + +<!--3 01365659472.98-01365661756.99-01365662958.100-01365663844.101-01365684929.102- --> +<LI><A HREF="000102.html">[99s-extend] Distributed model? +</A><A NAME="102"> </A> +<I>Lee Sylvester +</I> + +<!--3 01365659472.98-01365661756.99-01365662958.100-01365663844.101-01365684929.102-01365695195.103- --> +<LI><A HREF="000103.html">[99s-extend] Distributed model? +</A><A NAME="103"> </A> +<I>Lee Sylvester +</I> + +</UL> +</UL> +</UL> +<!--0 01365723438.104- --> +<LI><A HREF="000104.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="104"> </A> +<I>Brown, Kevin +</I> + +<UL> +<!--1 01365723438.104-01365725246.105- --> +<LI><A HREF="000105.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="105"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01365723438.104-01365725246.105-01365726615.106- --> +<LI><A HREF="000106.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="106"> </A> +<I>Brown, Kevin +</I> + +</UL> +<!--1 01365723438.104-01365851559.107- --> +<LI><A HREF="000107.html">[99s-extend] populating #http_req for unit testing +</A><A NAME="107"> </A> +<I>Eduardo Gurgel +</I> + +</UL> +<!--0 01366058742.108- --> +<LI><A HREF="000108.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="108"> </A> +<I>rambocoder +</I> + +<UL> +<!--1 01366058742.108-01366058867.109- --> +<LI><A HREF="000109.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="109"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01366058742.108-01366058867.109-01366071224.110- --> +<LI><A HREF="000110.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="110"> </A> +<I>rambocoder +</I> + +<UL> +<!--3 01366058742.108-01366058867.109-01366071224.110-01366112054.111- --> +<LI><A HREF="000111.html">[99s-extend] Reading body_qs multiple times +</A><A NAME="111"> </A> +<I>Loïc Hoguin +</I> + +</UL> +</UL> +</UL> +<!--0 01366382829.112- --> +<LI><A HREF="000112.html">[99s-extend] Cowboy CORS +</A><A NAME="112"> </A> +<I>Lee Sylvester +</I> + +<UL> +<!--1 01366382829.112-01366384083.113- --> +<LI><A HREF="000113.html">[99s-extend] Cowboy CORS +</A><A NAME="113"> </A> +<I>Phillips, Christopher +</I> + +</UL> +<!--0 01366635594.114- --> +<LI><A HREF="000114.html">[99s-extend] 505 error +</A><A NAME="114"> </A> +<I>Lee Sylvester +</I> + +<UL> +<!--1 01366635594.114-01366640891.115- --> +<LI><A HREF="000115.html">[99s-extend] 505 error +</A><A NAME="115"> </A> +<I>Brown, Kevin +</I> + +<UL> +<!--2 01366635594.114-01366640891.115-01366641619.116- --> +<LI><A HREF="000116.html">[99s-extend] 505 error +</A><A NAME="116"> </A> +<I>Lee Sylvester +</I> + +<UL> +<!--3 01366635594.114-01366640891.115-01366641619.116-01366646024.117- --> +<LI><A HREF="000117.html">[99s-extend] 505 error +</A><A NAME="117"> </A> +<I>Loïc Hoguin +</I> + +<!--3 01366635594.114-01366640891.115-01366641619.116-01366646111.118- --> +<LI><A HREF="000118.html">[99s-extend] 505 error +</A><A NAME="118"> </A> +<I>Brown, Kevin +</I> + +<!--3 01366635594.114-01366640891.115-01366641619.116-01366646111.118-01366655408.119- --> +<LI><A HREF="000119.html">[99s-extend] 505 error +</A><A NAME="119"> </A> +<I>Lee Sylvester +</I> + +<!--3 01366635594.114-01366640891.115-01366641619.116-01366646111.118-01366655408.119-01366658379.120- --> +<LI><A HREF="000120.html">[99s-extend] 505 error +</A><A NAME="120"> </A> +<I>Loïc Hoguin +</I> + +</UL> +</UL> +</UL> +<!--0 01366861584.121- --> +<LI><A HREF="000121.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="121"> </A> +<I>yongboy +</I> + +<UL> +<!--1 01366861584.121-01366890135.122- --> +<LI><A HREF="000122.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="122"> </A> +<I>Loïc Hoguin +</I> + +<UL> +<!--2 01366861584.121-01366890135.122-01366955820.123- --> +<LI><A HREF="000123.html">[99s-extend] does cowboy support hot code reload/replace ? +</A><A NAME="123"> </A> +<I>yongboy +</I> + +</UL> +</UL> +<!--0 01366956716.124- --> +<LI><A HREF="000124.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A><A NAME="124"> </A> +<I>yongboy +</I> + +<UL> +<!--1 01366956716.124-01366981913.125- --> +<LI><A HREF="000125.html">[99s-extend] cowboy how to ruduce the memory usage per long-hold connection +</A><A NAME="125"> </A> +<I>rambocoder +</I> + +</UL> +<!--0 01366989692.126- --> +<LI><A HREF="000126.html">[99s-extend] [ANN] Cowboy 0.8.4 +</A><A NAME="126"> </A> +<I>Loïc Hoguin +</I> + +<!--0 01367348361.127- --> +<LI><A HREF="000127.html">[99s-extend] cowboy websocket and wamp +</A><A NAME="127"> </A> +<I>Gregory de Souza +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Tue Apr 30 20:59:21 CEST 2013</i><br> + <b>Archived on:</b> <i>Wed May 28 18:41:43 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> + |