use timer phase to control http client

Author: leafo

lapis/http.lua

@@ -1,9 +1,5 @@
 if ngx then
-  if ngx.config and ngx.config.is_console then
-    return require("lapis.nginx.resty_http")
-  else
-    return require("lapis.nginx.http")
-  end
+  return require("lapis.nginx.http")
 elseif package.loaded["lapis.running_server"] == "cqueues" then
   return require("http.compat.socket")
 else

lapis/http.moon

@@ -1,9 +1,5 @@
 if ngx
-  if ngx.config and ngx.config.is_console
-    -- the "location capture" client is not compatible with resty
-    require "lapis.nginx.resty_http"
-  else
-    require "lapis.nginx.http"
+  require "lapis.nginx.http"
 elseif package.loaded["lapis.running_server"] == "cqueues"
   require "http.compat.socket"
 else

lapis/nginx/http.lua

@@ -59,6 +59,10 @@ simple = function(req, body)
 end
 local request
 request = function(url, str_body)
+  local _exp_0 = ngx.get_phase()
+  if "timer" == _exp_0 then
+    return require("lapis.nginx.resty_http").request(url, str_body)
+  end
   local ltn12 = require("ltn12")
   local config = lapis_config.get()
   local start_time

lapis/nginx/http.moon

@@ -93,6 +93,15 @@ simple = (req, body) ->
   res.body, res.status, res.header
 
 request = (url, str_body) ->
+  -- handle phases not compatible with location.capture
+  -- NOTE: while we are testing resty_http integration we are only exposing in
+  -- timers. You will need to manually opt into lapis.nginx.resty_http to use
+  -- it in other phases for now, as you may want the existing behavior of an
+  -- error to be raised if you're doing http requests in weird places
+  switch ngx.get_phase!
+    when "timer"
+      return require("lapis.nginx.resty_http").request url, str_body
+
   ltn12 = require "ltn12"
 
   config = lapis_config.get!