Jiří Smolík

Hmm, that got me really thinking... Looks like I only just realized that each `sweat` command is independent, including the configuration. Sorry for the confusion :(. In that case yes,...

> This is the easiest path I guess. Idd, seems like it :). For my use-case, I think the third option is the best and I will, eventually, realize it....

Unfortunately, I didn't :(. Since around the time I closed the issue, I've been overwhelmed with duties and other software problems. Nevertheless, let me offer some thoughts: I think the...

> However, can we have just one option for this? Why did you include the --ssl-only option? The `--ssl` option would be used if the administrator would like to support...

@passiomatic Currently, I'm in the process of implementing this but I've encountered a slight problem... A `https://127.0.0.1:3333/login` call is very successful but the login form's action attribute still points to...

> We are close to a 1.0 release and the last thing I want is a breaking change of this magnitude. I understand but personally, I don't think there will...

__UPDATE:__ I figured out how to fix the WSGI problem and solution nr. 1 (see my last post) is almost finished :).

Despite the term SSL is commonly used to denote SSL/TLS, or even TLS alone, thank you... a good tidbit :). I'll change the parameter's name to `--https-only` in my PR.

In most cases, perhaps. I've never meant to push this solution at any cost (especially if redirection is problematic), but at the same time, I disagree with the statement: >...

Specifically, I'd like the hash classes to provide a mechanism for validating semantics (values). Using the above example: ``` ruby def title_valid?(value) value.length < 16 end def property_valid?(name, value) false...