Hi Hunter,
Replied to you on IRC. It’s unclear what the actual problem is. You’re describing the solution you tried, but not what you experienced and what you’re trying to solve. So, what’s the original issue? From: <[email protected]> on behalf of hunter morgan <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, 18 January 2017 at 9:07 To: Swagger <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: cors/authentication headers this copies something from IRC. just want to make sure it didn't get lost. hey a teammate and i were unable yesterday to get a locally running swagger-editor to supply authentication to an api we were trying to test. i tried adding config from http://enable-cors.org/server_nginx.html, specifically the contents of one of the second two if blocks, because nginx complained at the inclusion of ifs. must have something to do with the structure. maybe because it's reverse proxying back to a node restify api? I also tried http://enable-cors.org/server_expressjs.html on the node api, but still no love. the nginx and api are live, in another castle, so i suspect it's cors tripping us up. the import proxy setting, is that just for spec import, not for proxying try it out requests? i tried starting a local cors-it and using that in that config section as well, but it didn't seem to change anything. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
