Feature Request. Add absolute url request

Feature Request

@Url annotation hidden combining with baseUrl is a non-intuitive way. For instance it doesn’t allow request for dynamic urls - if there is no scheme provided, it adds baseUrl which breaks request.

Also for purposes of combining baseUrl with multiple paths - there are already paths in @Get, @Post annotations and @Path param.

Suggestions:

• Add new annotation @RelativeUrl and move there current @Url combining logic
  • Or even multiple annotations for each kind of combining (host relative, scheme relative, etc)
• Make @Url always work as absolute url.

Or kind of workaround:

• Add new annotation @AbsoluteUrl that will always work as absolute url.

[JakeWharton]

Then you should be using OkHttp’s API directly instead of Retrofit. Retrofit is for structured APIs and URLs known at compile-time.

[JakeWharton]

Can you provide a specific example that doesn’t work? Relative resolution, absolute resolution, full URLs all work today.

non-intuitive way

It’s the same as <a href=""> and pretty standard faire for resolving one URI against another.