Re: [reSIProcate] HeaderNames issue
Hi Yannick,
I ran the test code you posted against the trunk revision and did not reproduce a crash. The Parse Exception threw as expected, but it did not crash. When I look at the code the HeaderName array, is an array of Data objects - these objects self initialize to an empty string. From what I can tell, when you create a URI object that is not associated with any header the HeaderType is set to Headers::UNKNOWN (-1) - see Uri.cxx constructor line 60. When Headers::getHeaderName is called it adds 1 to the header type and references it in the Headers array. This should just access a Data object that represents an empty string. I'm not seeing the issue. Perhaps something else is causing memory corruption in your copy of the code?