Example request: https://api.example.com/users
Related response:
{
"data": [],
"links": {
"self": "http://api.example.com/users",
"first": "http://api.example.com/users",
"last": "http://api.example.com/users",
"prev": null,
"next": null
},
"jsonapi": {
"version": "1.0"
}
}This is happening while running lux 1.2.0 via ubuntu linux in AWS behind an Elastic Load balancer. Load balancer is the https termination point and traffic then runs to nginx on 80 which routes request to lux process on port 3000.
I'm guessing that since the internal request comes in on http is why the response contains http links but hope we could establish a standard to address this case. I think it's fairly standard to update the request a header that contains the original request url.
Example request:
https://api.example.com/usersRelated response:
{ "data": [], "links": { "self": "http://api.example.com/users", "first": "http://api.example.com/users", "last": "http://api.example.com/users", "prev": null, "next": null }, "jsonapi": { "version": "1.0" } }This is happening while running lux 1.2.0 via ubuntu linux in AWS behind an Elastic Load balancer. Load balancer is the https termination point and traffic then runs to nginx on 80 which routes request to lux process on port 3000.
I'm guessing that since the internal request comes in on http is why the response contains http links but hope we could establish a standard to address this case. I think it's fairly standard to update the request a header that contains the original request url.