fix(*) resolve a possible segfault in the FFI

Creating the `rctx` can happen when no `wasm{}` block is configured
(e.g. through the FFI in `init_worker`). For example,
`set_host_properties_handlers()` might be called (wrong and unlikely,
but possible).

Always assume `rctx` might not be created due to a `wasm{}` block.

Author: thibaultcha

src/http/ngx_http_wasm_module.c

@@ -584,11 +584,11 @@ ngx_http_wasm_rctx(ngx_http_request_t *r, ngx_http_wasm_req_ctx_t **out)
             rctx->sock_buffer_reuse = loc->socket_buffer_reuse;
             rctx->pwm_lua_resolver = loc->pwm_lua_resolver != NGX_CONF_UNSET
                                      ? loc->pwm_lua_resolver
-                                     : wcf->pwm_lua_resolver;
+                                     : wcf ? wcf->pwm_lua_resolver : 0;
 
         } else {
             /* fake request */
-            rctx->pwm_lua_resolver = wcf->pwm_lua_resolver;
+            rctx->pwm_lua_resolver = wcf ? wcf->pwm_lua_resolver : 0;
         }
     }
 #if (NGX_DEBUG)

src/wasm/ngx_wasm_core_module.c

@@ -532,7 +532,9 @@ ngx_wasm_core_ssl_conf(ngx_cycle_t *cycle)
     ngx_wasm_core_conf_t  *wcf;
 
     wcf = ngx_wasm_core_cycle_get_conf(cycle);
-    ngx_wasm_assert(wcf);
+    if (wcf == NULL) {
+        return NULL;
+    }
 
     return &wcf->ssl_conf;
 }