From c807880f7ac73f813b2660ea81a00f7712a4e793 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Mon, 29 Aug 2016 12:39:49 +0200 Subject: Add old mailing list archives --- archives/extend/2013-April/000116.html | 151 +++++++++++++++++++++++++++++++++ 1 file changed, 151 insertions(+) create mode 100644 archives/extend/2013-April/000116.html (limited to 'archives/extend/2013-April/000116.html') diff --git a/archives/extend/2013-April/000116.html b/archives/extend/2013-April/000116.html new file mode 100644 index 00000000..0375b7de --- /dev/null +++ b/archives/extend/2013-April/000116.html @@ -0,0 +1,151 @@ + + + + [99s-extend] 505 error + + + + + + + + + + +

[99s-extend] 505 error

+ Lee Sylvester + lee.sylvester at gmail.com +
+ Mon Apr 22 16:40:19 CEST 2013 +

+
+ +
Well, the below is the sent and return headers on the failing machine.  On a succeeding machine, the headers are
+
+Request URL:http://www.example.com
+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:http://www.test.com
+Referer:http://www.test.com/
+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" <Kevin.Brown at turner.com> wrote:
+
+> 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" <lee.sylvester at gmail.com> wrote:
+> 
+>> 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:http://www.example.com
+>> 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:http://www.test.com
+>> Referer:http://www.test.com/
+>> 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
+>> 
+>> _______________________________________________
+>> Extend mailing list
+>> Extend at lists.ninenines.eu
+>> http://lists.ninenines.eu:81/listinfo/extend
+>> 
+> 
+
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ -- cgit v1.2.3