If "host" is set up for a route, then the port is not respected on route generation.

[ZeeCoder]

Suppose I have a local web server on port 8888, while my production server is on the standard 80.

Generating an absolute url with

Routing.generate('news', {}, true);

would generate a proper absolute url, like: "http://localhost:8888/news"

By having a specific "host" in the routing.yml configuration however does not behave like this.

For example, having the following yml config:

news:
    resource: "@AppBundle/Controller/NewsController.php"
    type: annotation
    host: %news.domain%

Where "news.domain" is a parameter set to "news.example.org" on the production server and to "news.localhost" on the local machine, generating routes results in the following:

Routing.generate('news');
Routing.generate('news', {}, true);

// Production results
// -> "http://news.example.org" // OK

// Local results
// -> "http://news.localhost" // Instead of the expected "http://news.localhost:8888"

[bnd170]

I have the same problem, no way to do it in my local envoirment

[lenybernard]

same here 😿

[DerekRoth]

This seems to be the same issue as #167
Not only the port is not included in the generated URL but the host is always included even if it is the same as the current one.

[devFab]

I still have the same issue. any update or way to fix it?

[andrewtch]

Same here (still)

[sarramegnag]

It seems like it is the same for schemes. If you specify host but not schemes, http is forced even if you access website through https.

# Generates right https urls
subdomain:
    resource: 'subdomain/routing.yml'

# Generates wrong http urls
subdomain:
    resource: 'subdomain/routing.yml'
    host: '%subdomain%'

# Generates right https urls
subdomain:
    resource: 'subdomain/routing.yml'
    host: '%subdomain%'
    schemes: [https]