Bug 76271

Summary:	error prone dialogue on authentication screen
Product:	[iFolder] iFolder Denali	Reporter:	Victor Billings <vbillings>
Component:	Server Admin	Assignee:	Scott Reeves <sreeves>
Status:	VERIFIED FIXED	QA Contact:	Jared Allen <jpallen>
Severity:	Normal
Priority:	P5 - None
Version:	iFolder Denali
Target Milestone:	FCS
Hardware:	i586
OS:	SLES 9
Whiteboard:
Found By:	Component Test	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	this is a screencap of the current method of setting a port

Description Victor Billings 2005-04-07 22:54:53 UTC

Build : 0407 iF3e

Description : Currently the authentication prompt gives the user a checkbox if
they want to authenticate over a different port than 80 or 443. Wouldn't it make
more sense from a UI perspective to just have the format be
ipaddress:portnumber? We could even prepopulate the initial address with :443 to
make it obvious.

Expected Results : It took me a while to phrase this defect because I was so
used to this in the browser world. When someone wants to use a non-standard port
they simply put a colon after the ipaddress ie tomcat on :8080 It took a while
to realize that an additional dialogue was a weird way to do it for me.

Actual Results : 

Additional information : See attached screencap for more detail.

Comment 1 Victor Billings 2005-04-07 22:55:25 UTC

Created attachment 33407 [details]
this is a screencap of the current method of setting a port

Comment 2 Scott Reeves 2005-04-27 20:43:33 UTC

The issue is that we have no protocol field so this is not standard URL 
syntax. There is nowhere to specify secure or non secure port information via 
the standard syntax (ie http or https). Since we have to special case part of 
the standard specification it's no more ugly to have a simple name field entry 
and an additional optional information field (port, secure) than it is to 
support part of the additional syntax beyond simple name but not all.  

I will mark this bug fixed though instead of invalid as I improved the error 
message if they specify port or path information on the server name.

Comment 3 Victor Billings 2005-05-31 21:57:14 UTC

this is verified in the fcs build

Comment 4 Victor Billings 2005-06-17 20:33:55 UTC

this is released fixed in the fcs build