(regression) nested server directives when using SSL vhost

[3flex]

PR #184 changed the priority of the vhost file fragments, so the templates will be combined in this order when SSL vhost is used (first number is the priority):

• 001: nginx/vhost/vhost_header.erb
• 300: nginx/vhost/vhost_ssl_header.erb
• 699: nginx/vhost/vhost_footer.erb
• 999: nginx/vhost/vhost_ssl_footer.erb

The server directive and the relevant closing braces are now:

#vhost_header.erb
server {

#vhost_ssl_header.erb
server {

#vhost_footer.erb
}

#vhost_ssl_footer
}

This creates a nested server directive which is invalid.

[abraham1901]

Hmm. You're right, but to undo the changes mean return error. We need a different implementation priorities.
I'm trying rewrite it.

[3flex]

What error are you receiving? Could you include a copy of your manifest that's returning an error? If you outline the problem you're actually trying to solve because it will make working out a solution easier, in a way that won't cause regressions.

[abraham1901]

Sorry, it's my error.
I forgot to specify the option ssl => true for my location.
ssl priority algorithm right:
$ssl_priority = $priority + 300

ohohoh, I need more sleep ...
Sprinkle ashes.

And need changes user priority for location s/400-499, 501-599/401-499, 501-599/ in manual.

James, please merge this fix.