Skip to content
This repository is currently being migrated. It's locked while the migration is in progress.

Conversation

lneto
Copy link

@lneto lneto commented May 3, 2016

No description provided.

@lneto
Copy link
Author

lneto commented May 3, 2016

hey @kipras, could you please review this? Thanks!

@@ -241,6 +242,7 @@ struct ngx_http_upstream_check_srv_conf_s {
ngx_array_t *fastcgi_params;

ngx_uint_t default_down;
ngx_uint_t ssl;
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a boolean flag, so perhaps we can use ngx_uint_t ssl:1; here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's a boolean. Unfortunately, Nginx doesn't define (or use the standard) boolean type. I think using bit fields would make sense for a collection of flags, not for a single one.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, but if there was another boolean flag to be added - the we wouldn't have to modify this one :)
Also, default_down looks like a boolean flag too.
But anyway, this is a very minor thing and can be skipped :)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed for having both default_down and ssl, but I would skip this change to avoid changing unnecessary things. IMHO, it makes it hard to sync with upstream.

@kipras
Copy link

kipras commented May 4, 2016

Looks great, i didn't test it though.

@kipras kipras assigned lneto and unassigned kipras May 4, 2016
@lneto lneto merged commit b085ca1 into master May 9, 2016
@bekinin bekinin deleted the lua_656_https branch May 11, 2016 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants