Yes, it might work well to just leave the protocol field as a text field
where the user can enter whatever he wants, as it is today.
So the "novice" users will continue to enter either http or https.
And people who read the documentation will write "http(tls)", for
example, I assume it will remain case insensitive.
So I favour your suggestion, Sebb.
Regards
Alf Hogemark
sebb wrote:
On 17/03/07, Alf Høgemark <[EMAIL PROTECTED]> wrote:
This discussion about TLS / SSL seems related to
:http://issues.apache.org/bugzilla/show_bug.cgi?id=39638
Agreed.
If Sebb's fix works, and he can suggest how he wants the GUI changed for
the "HTTP Request parameters", I can probably look into making a
patch for
allowing the user to specify what https mode to use.
You suggestion on different dropdown values are one option, another one
would be to have a separate dropdown for "HTTPS mode" or something.
For backward compatibility we need to keep the exisiting protocol field.
One could add the SSL protocol as a part of the field, e.g.
HTTPS
HTTPS(TLS)
HTTPS(SSLv1)
etc. No need to change the GUI - only the code (and documentation).
The advantage is that any protocol could be selected this way, also it
would be easy to use a variable.
I'm not sure about a drop-down list; this would make the GUI look more
complicated.
WDYT?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
