Invalid hostname when warming application

[tmaier]

My heroku app has two domains: example.herokuapp.com and *.example.com. Paratrooper seems to use the last one when warming the application.

I get the following error:

============================================================
>> Accessing *.example.com to warm up your application
============================================================

rake aborted!
URI::InvalidURIError: the scheme http does not accept registry part: *.example.com (or bad hostname?)

require 'uri'
URI('http://*.example.com')
# => URI::InvalidURIError: the scheme http does not accept registry part: *.example.com (or bad hostname?)
#    from /usr/local/opt/rbenv/versions/2.1.1/lib/ruby/2.1.0/uri/generic.rb:214:in `initialize'

Possible solutions:

• app_url should be something different if last domain starts with a star character
• Allow to set a :warming_uri (instead of just :protocol)

[knwang]

@mattpolito do we need warming up apps? I am not sure the app is ever "cold" after deploy

[mattpolito]

Well, the idea was that you would hit the dyne the first time with the warmup call before your users would but that has not been the case. With the requests getting queued it appears that the warmup call a lot of times goes to the old dyne instead of the new one. I've been toying with the idea of removing it.