Spider fails to start (footer panel) with a site accessed over a secure connection (HTTPS) on a non-default port

[GoogleCodeExporter]

Steps to reproduce the issue:
1. Run ZAP;
2. Access a site over a secure connection on a non-default port (example: 
https://example.com:8888/);
3. Select the "Spider" tab and choose the accessed site ("Site" combo box);
4. Press the "Start Spider" button ("play");
5. The spider seems to start but nothing happens. An error is logged:
[...]
116347 [Thread-8] INFO org.zaproxy.zap.extension.spider.SpiderThread  - 
Starting spidering scan on example.com:8888 at Mon Apr 13 00:30:17 WEST 2013
116347 [Thread-8] ERROR org.zaproxy.zap.extension.spider.SpiderThread  - Spider 
cannot start - No start node set for site example.com:8888
[...]

Remarks:
The site can still be "spidered" using the API or the main pop up menu options 
"Attack" > "Spider [...]".

ZAP Version:
Version 2.0.0 (and trunk r3020).

Original issue reported on code.google.com by THC...@gmail.com on 8 Apr 2013 at 4:01

[GoogleCodeExporter]

r4515

Original comment by THC...@gmail.com on 28 Mar 2014 at 3:06

• Changed state: Committed

[GoogleCodeExporter]

Original comment by psii...@gmail.com on 31 Mar 2014 at 11:17

• Added labels: Build-20140327

[GoogleCodeExporter]

Fixed in ZAP 2.3.0

Original comment by psii...@gmail.com on 10 Apr 2014 at 3:25

• Changed state: Fixed