Searched hist:693 (Results 1 – 12 of 12) sorted by relevance
| /unit/test/go/404/ |
| H A D | 404.html | 693:e25fe62e9efb Fri Jun 08 15:32:00 UTC 2018 Andrey Zelenkov <zelenkov@nginx.com> Tests: Go application tests.
|
| H A D | app.go | 693:e25fe62e9efb Fri Jun 08 15:32:00 UTC 2018 Andrey Zelenkov <zelenkov@nginx.com> Tests: Go application tests.
|
| /unit/test/go/command_line_arguments/ |
| H A D | app.go | 693:e25fe62e9efb Fri Jun 08 15:32:00 UTC 2018 Andrey Zelenkov <zelenkov@nginx.com> Tests: Go application tests.
|
| /unit/test/go/cookies/ |
| H A D | app.go | 693:e25fe62e9efb Fri Jun 08 15:32:00 UTC 2018 Andrey Zelenkov <zelenkov@nginx.com> Tests: Go application tests.
|
| /unit/test/go/empty/ |
| H A D | app.go | 693:e25fe62e9efb Fri Jun 08 15:32:00 UTC 2018 Andrey Zelenkov <zelenkov@nginx.com> Tests: Go application tests.
|
| /unit/test/go/get_variables/ |
| H A D | app.go | 693:e25fe62e9efb Fri Jun 08 15:32:00 UTC 2018 Andrey Zelenkov <zelenkov@nginx.com> Tests: Go application tests.
|
| /unit/test/go/mirror/ |
| H A D | app.go | 693:e25fe62e9efb Fri Jun 08 15:32:00 UTC 2018 Andrey Zelenkov <zelenkov@nginx.com> Tests: Go application tests.
|
| /unit/test/go/post_variables/ |
| H A D | app.go | 693:e25fe62e9efb Fri Jun 08 15:32:00 UTC 2018 Andrey Zelenkov <zelenkov@nginx.com> Tests: Go application tests.
|
| /unit/test/go/variables/ |
| H A D | app.go | 693:e25fe62e9efb Fri Jun 08 15:32:00 UTC 2018 Andrey Zelenkov <zelenkov@nginx.com> Tests: Go application tests.
|
| /unit/test/ |
| H A D | test_go_application.py | 693:e25fe62e9efb Fri Jun 08 15:32:00 UTC 2018 Andrey Zelenkov <zelenkov@nginx.com> Tests: Go application tests.
|
| /unit/src/ |
| H A D | nxt_http_variables.c | diff 2158:bbc15554fb36 Fri May 06 18:41:00 UTC 2022 Andrew Clayton <andrew@digital-domain.net> Var: added a $dollar variable that translates to a '$'.
Allow $dollar (or ${dollar}) to translate to a literal $ to allow
support for sub-delimiters in URIs.
It is possible to have URLs like
https://example.com/path/15$1588/9925$2976.html
and thus it would be useful to be able to specify them in various bits
of the unit config such as the location setting.
However this hadn't been possible due to $ being used to denote
variables for substitution. E.g $host.
As was noted in the below GitHub issue it was suggested by @VBart to
use $sign to represent a literal $, however I feel $dollar is more
appropriate so we have a variable named after the thing it represents,
also @tippexs found[0] that &dollar is used in HTML to represent a $, so
there is some somewhat related precedent.
(The other idea to use $$ was rejected in my original pull-request[1]
for this issue.)
This means the above URL could be specified as
https://example.com/path/15${dollar}1588/9925${dollar}2976.html
in the unit config.
This is done by adding a variable called 'dollar' which is loaded into
the variables hash table which translates into a literal $.
This is then handled in nxt_var_next_part() where variables are parsed
for lookup and $dollar is set for substitution by a literal '$'. Actual
variable substitution happens in nxt_var_query_finish().
[0]: https://github.com/nginx/unit/pull/693#issuecomment-1130412323
[1]: https://github.com/nginx/unit/pull/693
Closes: https://github.com/nginx/unit/issues/675
diff 2158:bbc15554fb36 Fri May 06 18:41:00 UTC 2022 Andrew Clayton <andrew@digital-domain.net> Var: added a $dollar variable that translates to a '$'.
Allow $dollar (or ${dollar}) to translate to a literal $ to allow
support for sub-delimiters in URIs.
It is possible to have URLs like
https://example.com/path/15$1588/9925$2976.html
and thus it would be useful to be able to specify them in various bits
of the unit config such as the location setting.
However this hadn't been possible due to $ being used to denote
variables for substitution. E.g $host.
As was noted in the below GitHub issue it was suggested by @VBart to
use $sign to represent a literal $, however I feel $dollar is more
appropriate so we have a variable named after the thing it represents,
also @tippexs found[0] that &dollar is used in HTML to represent a $, so
there is some somewhat related precedent.
(The other idea to use $$ was rejected in my original pull-request[1]
for this issue.)
This means the above URL could be specified as
https://example.com/path/15${dollar}1588/9925${dollar}2976.html
in the unit config.
This is done by adding a variable called 'dollar' which is loaded into
the variables hash table which translates into a literal $.
This is then handled in nxt_var_next_part() where variables are parsed
for lookup and $dollar is set for substitution by a literal '$'. Actual
variable substitution happens in nxt_var_query_finish().
[0]: https://github.com/nginx/unit/pull/693#issuecomment-1130412323
[1]: https://github.com/nginx/unit/pull/693
Closes: https://github.com/nginx/unit/issues/675
|
| /unit/docs/ |
| H A D | changes.xml | diff 2158:bbc15554fb36 Fri May 06 18:41:00 UTC 2022 Andrew Clayton <andrew@digital-domain.net> Var: added a $dollar variable that translates to a '$'.
Allow $dollar (or ${dollar}) to translate to a literal $ to allow
support for sub-delimiters in URIs.
It is possible to have URLs like
https://example.com/path/15$1588/9925$2976.html
and thus it would be useful to be able to specify them in various bits
of the unit config such as the location setting.
However this hadn't been possible due to $ being used to denote
variables for substitution. E.g $host.
As was noted in the below GitHub issue it was suggested by @VBart to
use $sign to represent a literal $, however I feel $dollar is more
appropriate so we have a variable named after the thing it represents,
also @tippexs found[0] that &dollar is used in HTML to represent a $, so
there is some somewhat related precedent.
(The other idea to use $$ was rejected in my original pull-request[1]
for this issue.)
This means the above URL could be specified as
https://example.com/path/15${dollar}1588/9925${dollar}2976.html
in the unit config.
This is done by adding a variable called 'dollar' which is loaded into
the variables hash table which translates into a literal $.
This is then handled in nxt_var_next_part() where variables are parsed
for lookup and $dollar is set for substitution by a literal '$'. Actual
variable substitution happens in nxt_var_query_finish().
[0]: https://github.com/nginx/unit/pull/693#issuecomment-1130412323
[1]: https://github.com/nginx/unit/pull/693
Closes: https://github.com/nginx/unit/issues/675
diff 2158:bbc15554fb36 Fri May 06 18:41:00 UTC 2022 Andrew Clayton <andrew@digital-domain.net> Var: added a $dollar variable that translates to a '$'.
Allow $dollar (or ${dollar}) to translate to a literal $ to allow
support for sub-delimiters in URIs.
It is possible to have URLs like
https://example.com/path/15$1588/9925$2976.html
and thus it would be useful to be able to specify them in various bits
of the unit config such as the location setting.
However this hadn't been possible due to $ being used to denote
variables for substitution. E.g $host.
As was noted in the below GitHub issue it was suggested by @VBart to
use $sign to represent a literal $, however I feel $dollar is more
appropriate so we have a variable named after the thing it represents,
also @tippexs found[0] that &dollar is used in HTML to represent a $, so
there is some somewhat related precedent.
(The other idea to use $$ was rejected in my original pull-request[1]
for this issue.)
This means the above URL could be specified as
https://example.com/path/15${dollar}1588/9925${dollar}2976.html
in the unit config.
This is done by adding a variable called 'dollar' which is loaded into
the variables hash table which translates into a literal $.
This is then handled in nxt_var_next_part() where variables are parsed
for lookup and $dollar is set for substitution by a literal '$'. Actual
variable substitution happens in nxt_var_query_finish().
[0]: https://github.com/nginx/unit/pull/693#issuecomment-1130412323
[1]: https://github.com/nginx/unit/pull/693
Closes: https://github.com/nginx/unit/issues/675
|