[www/nginx] Add url and urltable to trusted-proxy-alias dropdown

[PrivatePuffin]

Quick fix adding the url and urltable alias types to the dropdown selecting trusted-proxy firewall aliasses in NGINX.

As discussed here:
https://forum.opnsense.org/index.php?topic=14617.msg71645#msg71645

Signed-off-by: Kjeld Schouten-Lebbing kjeld@schouten-lebbing.nl

[fabianfrz]

This is likely not possible because nginx cannot handle this types. The aliases of host and network are stored in the config.xml while the table types are external and need to be fetched first. The nginx template cannot fetch such tables and for that reason, it is likely not going to work - even if you can select it by the model.

[fabianfrz]

Please have a look at the backend template as well:

https://github.com/opnsense/plugins/blob/master/www/nginx/src/opnsense/service/templates/OPNsense/Nginx/http.conf#L139

[PrivatePuffin]

It might sound harsh, but that makes it totally useless with most reverse proxy providers...
Because those often use iplists that might change

Closing because i don't have the time to do a refactor of this.

[PrivatePuffin]

I don't get why it doesn't use the API to grab the alias.

Assuming my alias is named "proxy_trusted_ips", I can just grab it like this:
https://router.local/api/firewall/alias_util/list/proxy_trusted_ips

Which gives me:
{"total":21,"rowCount":9999,"current":1,"rows":[{"ip":"103.21.244.0\/22"},{"ip":"103.22.200.0\/22"},{"ip":"103.31.4.0\/22"},{"ip":"104.16.0.0\/12"},{"ip":"108.162.192.0\/18"},{"ip":"131.0.72.0\/22"},{"ip":"141.101.64.0\/18"},{"ip":"162.158.0.0\/15"},{"ip":"172.64.0.0\/13"},{"ip":"173.245.48.0\/20"},{"ip":"188.114.96.0\/20"},{"ip":"190.93.240.0\/20"},{"ip":"197.234.240.0\/22"},{"ip":"198.41.128.0\/17"},{"ip":"2400:cb00::\/32"},{"ip":"2405:8100::\/32"},{"ip":"2405:b500::\/32"},{"ip":"2606:4700::\/32"},{"ip":"2803:f800::\/32"},{"ip":"2a06:98c0::\/29"},{"ip":"2c0f:f248::\/32"}]}

Which is type independent and pretty well parseable... So why has someone somehow made a choice to grab it from config.xml in the damn first place? This seems like a very dirty hack to me.