possible regression introduce by FaaSController about easegress HOT 3 CLOSED

Yes, we have fixed that problem, will merge it in the next PR. Thx

from easegress.

@tg123 Thanks

• In the original PR, I notice the mux package has a potential problem for handling requests even in the header-not-match scenario. So I remove it and create a discussion related to it. But it had been merged without full discussion and testing.
• For a stable usage scenario, please use the 1.0.0 tag version's Easegress, and I will open a new issue for this not feature-related modification next time.

BTW: the correct logic here should be if there are headers related setting, not match will cause a 404, else it is a path matching. We will fix it in the next PR.

from easegress.

@tg123 We had launched the fixing PR #76, and in normal path-matching(Readme example) and header-matching(FaaSController) scenarios, Easegress can work as expected.

Thanks for reporting this bug again. :-)

from easegress.