Marco Ebert
Marco Ebert
The original RegEx also checks for ports in the host part. No idea if this might break it.
I just played around a bit for 5min and these are all the possible strings that I could come up with, that would match: https://regex101.com/r/4VTkr0/1. ``` https://GACKOgacko123456789-gacko.domain.COM:80/ABCdef123-.txt http://GACKOgacko123456789-gacko.domain.COM:80/ABCdef123-.txt GACKOgacko123456789-gacko.domain.COM:80/ABCdef123-.txt https://:80/ABCdef123-.txt...
How about this RegEx: https://regex101.com/r/HElwMt/1 `^(https?://[A-Za-z0-9\-.]+(:\d+)?)?(/[A-Za-z0-9\-.]+)*/?$` It matches only: ``` / /errors /errors/ /errors/page /errors/page/ /errors/page.html http://github.com https://github.com http://github.com:80 https://github.com:443 http://github.com/ https://github.com/ http://github.com:80/ https://github.com:443/ http://github.com/errors https://github.com/errors http://github.com:80/errors https://github.com:443/errors http://github.com/errors/ https://github.com/errors/...
I added the `_` to the RegEx, see the before mentioned PR.
Yes. Also because I haven't reviewed it nor think it's just a patch.
It starts failing because we enabled annotation validation by default in v1.12.0. Apart from that I currently cannot help a lot nor take a deeper look into the issue.
From your bug description I get the strong feeling that it has something to do with DNS. The issue occurs right after you update a CNAME record's value and you're...
Ingress NGINX is provider agnostic, we are not setting any provider specific annotations and only create a plain Kubernetes service resource, so provider implementation depends on your cloud controller.