-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crash #29
Comments
@mu326668629 Will you provide a sample nginx.conf snippet that can trigger this? Thanks! |
@mu326668629 I don't see how you can end up getting |
location =/modify { 127.0.0.1/modify?status=3 |
@mu326668629 Your nginx.conf snippet contains syntax error which won't even load. Will you provide a snippet that you have actually tested on your side? Thanks! |
@mu326668629 Also, BTW, please use the markdown syntax for code snippets. |
@mu326668629 From what you've provided, I can see the problem is the use of the Also, BTW, "if is evil": https://www.nginx.com/resources/wiki/start/topics/depth/ifisevil/ Better avoid it than sorry. |
I also find this issue when using 'if' in the conf file. |
ngx_http_drizzle_create_loc_conf(ngx_conf_t *cf){
conf->complex_target = NGX_CONF_UNSET_PTR;//0xffffffffffffffff
}
ngx_int_t
ngx_http_drizzle_handler(ngx_http_request_t r){
if (dlcf->complex_target) {//0xffffffffffffffff
/ variables used in the drizzle_pass directive */
if (ngx_http_complex_value(r, dlcf->complex_target, &target)
!= NGX_OK) //cash here..
{
dd("failed to compile");
return NGX_ERROR;
}
}
The text was updated successfully, but these errors were encountered: