Callback URLs should allow for Port Number to be specified

[GoogleCodeExporter]

What steps will reproduce the problem?

On a locally installed pubsubhubbub server, using the Subscribe page, any 
callback that explicity defines the port number displays an exception in 
the console window.  Omitting the port number and using the standard port 
number works fine.  Of course, the callback is properly configured for 
each port.

e.g.
http://localhost/mycallback.asp
works fine

but
http://localhost:81/mycallback.asp
causes the exception

What is the expected output? What do you see instead?
This is the traceback generated:
ERROR    2009-08-13 01:44:19,914 main.py:1361] Error encountered while 
confirming subscription
Traceback (most recent call last):
  File "C:\pubsubhubbub\hub\main.py", line 1359, in confirm_subscription
    follow_redirects=False)
  File "C:\Program 
Files\Google\google_appengine\google\appengine\api\urlfetch.p
y", line 241, in fetch
    return rpc.get_result()
  File "C:\Program 
Files\Google\google_appengine\google\appengine\api\apiproxy_s
tub_map.py", line 458, in get_result
    return self.__get_result_hook(self)
  File "C:\Program 
Files\Google\google_appengine\google\appengine\api\urlfetch.p
y", line 325, in _get_fetch_result
    raise DownloadError(str(err))
DownloadError: ApplicationError: 2 (11001, 'getaddrinfo failed')

What version of the product are you using? On what operating system?
pubsubhubserver on Windows Vista 32-bit with google app engine 1.2.4 and 
python 2.5.4

Please provide any additional information below.

Original issue reported on code.google.com by ssidera...@gmail.com on 13 Aug 2009 at 2:19

[GoogleCodeExporter]

Original comment by bslatkin on 20 Aug 2009 at 6:20

• Changed state: Accepted

[GoogleCodeExporter]

I didnt see this before submitting a patch to issue 54. This issue might be 
related.

Original comment by alex.schoof on 21 Aug 2009 at 1:55

[GoogleCodeExporter]

Issue 54 has been merged into this issue.

Original comment by bslatkin on 25 Aug 2009 at 2:59

[GoogleCodeExporter]

This should be fixed in r227 (which I'll push to production for the demo hub 
soon)

Original comment by bslatkin on 25 Aug 2009 at 5:43

• Changed state: Fixed