(non-default) port missing with absolute URLs (e.g. in schema URL)

[blueyed]

request.build_absolute_uri() is used in e.g. SchemaGenerator.get_schema(), but this does not include the port being used.

This is bad when using e.g. the coreapi-cli client against a local runserver instance, where links cannot be resolved then.

While the port could be included on Django's side maybe, it might be better to use get_raw_uri() instead?!

[rpkilby]

Hi @blueyed. Off the cuff, this doesn't sound correct. Both request.build_absolute_uri() and request.get_raw_uri() ultimately make calls to request._get_raw_host(), which is what is used to return the HOST+PORT.

[blueyed]

@rpkilby
You're right - so it would likely not help to use get_raw_uri() then, and I need to investigate if and why _get_raw_host() does not work.

[rpkilby]

Sounds good. I'm going to close this for now, since this sounds like a configuration issue.

[blueyed]

It turned out to be a bug in coreapi-cli when using --debug.. core-api/coreapi-cli#22