4 ms·
Have you read their incident response? If you had, you would know they weren't using Go for this and it was actually an issue an a parser generated by ragel (C
by ecnahc515 10y ago
Have you read their incident response? If you had, you would know they weren't using Go for this and it was actually an issue an a parser generated by ragel (C++) which was then used as an nginx module.
- turbohedgehog 10y agoTo be clear, it was mis-use of Ragel, not the fault of the Ragel module