Variable $request_uri is not defined when used inside js expression about unit HOT 7 OPEN

Hi,
Take a look at the document (https://unit.nginx.org/scripting/#scripting).
There are only a few common variables supported for now.

Btw, we'll support the variables accessing with njs in the next version.
Here's the PR(#1024), welcome to try it.

from unit.

Good morning! The uri does NOT include the arguments. We have to use request_uri for that. The request_uri will be available in NJS within the next release as mentioned.

Furthermore I think it will be benefitial for everybody if we would provide NJS functions in files easy to consume for such use cases.

Without saying: We have to provide a easy to use solution for such use cases for users like @veremax! So, thanks for testing this @veremax and letting us know. We are working on a solution that will make this A LOT! easier with Unit 1.32 which we are about to ship within the next 4 weeks.

from unit.

I think we should keep this issue open as long as we are working on resolving the issue with the request arguments and rewrites.

from unit.

@tippexs Are there cleaner ways to strip www. from hostnames and provide http->https redirection?

from unit.

For compactness (don't hate me!)

{
  "action": {
    "return": 301,
    "location": "`${'https://' + host.substr(host.startsWith('www.')*4) + uri}`"
  }
}

from unit.

For compactness (don't hate me!)

{
  "action": {
    "return": 301,
    "location": "`${'https://' + host.substr(host.startsWith('www.')*4) + uri}`"
  }
}

Unfortunately, after redirection you will lose parameters after "?" (query_string)

from unit.

@tippexs @lcrilly @hongzhidao @
Thank you very much!

from unit.