Eliminating shift/reduce conflict in bison parser
I am working on defining a bison grammar for http and am dealing with a number of shift/reduce conflicts with regards to how optional whitespace is handled at the end of the header field value. Here is a simplified version of the grammar that just deals with the header field portion: