Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed

* [sup-talk] header parsing
@ 2008-02-17 22:44 Daniel Wagner
  2008-02-18 14:33 ` William Morgan
  0 siblings, 1 reply; 2+ messages in thread
From: Daniel Wagner @ 2008-02-17 22:44 UTC (permalink / raw)


Hello,

Can sup be a bit more lax on parsing email headers?  In particular, it
seems to discard any where the ':' is not immediately followed by a ' '.
I'm not totally sure of the spec, but I couldn't find anything in
<http://tools.ietf.org/html/rfc2822#section-2.2> that required a space
after the colon.  (Granted, I did do a very cursory look.)

Thanks,
~d


^ permalink raw reply	[flat|nested] 2+ messages in thread

• * [sup-talk] header parsing
    2008-02-17 22:44 [sup-talk] header parsing Daniel Wagner
  @ 2008-02-18 14:33 ` William Morgan
    0 siblings, 0 replies; 2+ messages in thread
  From: William Morgan @ 2008-02-18 14:33 UTC (permalink / raw)
  
  
  Reformatted excerpts from Daniel Wagner's message of 2008-02-17:
  > Can sup be a bit more lax on parsing email headers?  In particular, it
  > seems to discard any where the ':' is not immediately followed by a '
  > '.  I'm not totally sure of the spec, but I couldn't find anything in
  > <http://tools.ietf.org/html/rfc2822#section-2.2> that required a space
  > after the colon.  (Granted, I did do a very cursory look.)
  
  Funny, I encountered this today too. I've merged in a change to next.
  
  -- 
  William <wmorgan-sup at masanjin.net>
  
  
  ^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-02-18 14:33 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-17 22:44 [sup-talk] header parsing Daniel Wagner
2008-02-18 14:33 ` William Morgan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox