You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Colons are not considered word characters, so most tables will never have ":" in its token list. Attachment filenames are the only exception to this; they bypass the usual tokenization logic.
I will fix this as part of my pull request for rc0#13 because the new pattern it will introduce uses colons to delineate header names.
The text was updated successfully, but these errors were encountered:
I closed my pull request since it didn't seem to be getting any attention, but I noticed there's been a couple of recent commits, so I'm commenting on this issue in hopes that you (@vandry) will have time to review my changes in #12.
Parse out the examples from the config man page, then run them through
the config parser to make sure that they at least parse correctly. It's
embarrassing to have mistakes in the example configs!
Also fix the missing "apply-" in the example configuration for
dns-servers in the DHCP configuration. (Fixes: #11)
Colons are not considered word characters, so most tables will never have ":" in its token list. Attachment filenames are the only exception to this; they bypass the usual tokenization logic.
I will fix this as part of my pull request for rc0#13 because the new pattern it will introduce uses colons to delineate header names.
The text was updated successfully, but these errors were encountered: