-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regexp-based proxy #824
Comments
Nevermind, looks like this was already actually added, just not very well documented (I couldn't see anything in any of the examples about regex/pattern support). 6679b02#diff-d54fbf1585a1667e6b2bd2e62cc655f4007a4d20092da622464af114b2bea527R181
|
@Warr1024 @aler9 Sorry, I did not get, did you able to resolve this? When I'm trying to use regexp in the proxy (similarly to your example), I'm getting For example. My camera can publish two streams: |
UPDATE:
In this case all that supplied in input URL will be appended to the source URL: I guess this solution is much simplier to implement than the previous one. |
Hi, Just want to clarify Is this currently not possible on the latest version ? paths:
"~^siteA-([0-9]{1})$":
source: rtsp://siteAPIP/cam/realmonitor?channel=$G1
sourceOnDemand: yes |
@wiryonolau You had my hopes up for a moment. I tried a variant of your example, and ended up with:
|
Yep it happen to me too. I try using runOnInit but it's also not working. The documentation in the config is not clear btw. Currently I write all the camera one by one, almost 200 and growing :D. |
i have over 1570 streams and i dont see finish... please developed... need it like air... paths:
"~^([0-9]{20}|[0-9][0-9][5])$":
source: rtsp://site_or_ip:port/~^([0-9]{20})$
sourceProtocol: tcp I would also like to fix this |
put keys between double quotes, or even better, generate the YAML file by using a library. |
Currently per |
This allows to proxy requests to other servers by using regular expressions.
This allows to proxy requests to other servers by using regular expressions.
This allows to proxy requests to other servers by using regular expressions.
This allows to proxy requests to other servers by using regular expressions.
This allows to proxy requests to other servers by using regular expressions.
This issue is mentioned in release v1.4.0 🚀 |
This issue is being locked automatically because it has been closed for more than 6 months. |
Describe the feature
Building on #54 it would be nice to be able to automatically build a proxy rule:
I'm using a capture group in the example above, I'm not quite sure how yaml handles
\
escapes characters, but that should be fine before a number.An alternative for me is to generate a configuration file with all the possible paths, but that's a lot less flexible.
Of course, there might be some security considerations (XSS/CSRF-class, as well as "SQL injection"-like).
The text was updated successfully, but these errors were encountered: