Recent Changes
Recent Changes · Search:
 
Summary
Running webserver on port other than 80 causes Configuration.pm to throw error
Type
Bug
Raised by
AJC?
Date opened
Friday, 19 January 2007
Description
Referencing wikibook-0.9.4b

When running a webserver on a port other than 80, the port must be specified in the url like this: http://server:port/page/to/look/at. However, when a port is specified, Configuration.pm returns the error message “Does not appear to be a valid URL.” This is difficult to deal with in a situation where the Internet provider is blocking port 80 outbound.

This seems to be caused by the regex on line 101 ( $v !~ /^https?\:\/\/[a-z0-9\.\-]+\//) which does not allow a colon (:) to appear anywhere in the URL after the protocol is specified.

Importance
3
Proposed solution
Permit a colon to appear in the URL after the protocol is specified. This could be done by adding a colon to the latter portion of the regex.

If this were implemented, you might change this

( $v !~ /^https?\:\/\/[a-z0-9\.\-]+\//)

to read this

( $v !~ /^https?\:\/\/[a-z0-9\:\.\-]+\//)

The difference between the two expressions is highlighted in red here:

( $v !~ /^https?\:\/\/[a-z0-9\:\.\-]+\//)

Urgency
3
Status
Closed
Resolution
Fixed in release 0.9.4c (Tuesday, 27 February 2007) — available for download from Install the Server.
Date closed
Tuesday, 27 February 2007

« 00098 · Edit Form · 00100 »

Page last modified on 27 February 2007 at 12:03 PM