Note that it may be even more important to support schemes other than https.

Maybe we could address all of this by changing the way we save configuration files, from com/example/www/ to simply www.example.com/.

This way, ports may be specified as www.example.com:8080.

Schemes may be less straightforward to specify, as https://www.example.com/ would not be a valid path. Maybe just https:www.example.com.

The reason why we have paths defined as com/example/www/ is probably because we wanted Web2Cit to use configuration files hierarchically (i.e., use com.example.com.sub, if not available use com.example.com, else use com.example). But then plans changed.

Finally, note that we may still support these and other use cases with the current approach, though. For example: com:8080/example/http:diegodlh@www/

Or, alternatively, to preserve the hierarchy, because scheme, port and userinfo refer to ways of accessing the same host:

• com/example/www/http:/
• com/example/www/diegodlh@
• com/example/www/:8080/
• any combination: com/example/www/http:diegodlh@:8080/