This wouldn't qualify as an "obvious" bug if the RFC stipulated that all parts of type "application/type" had to have a blank line before the boundary. I have no idea if it does or doesn't, of course. But that would be something very hard to know and be "non-obvious."
At any rate, Google seems to require the extra blank line. Either they have deviated from the RFC or team Mojolicious has. Google isn't known for overlooking obvious bugs either. On Tuesday, September 18, 2018 at 2:52:59 PM UTC-4, sri wrote: > > Now the question is, is this a mojolicious bug or not? Is the content >> inside of a multipart post request required to have a blank line after it? >> > > We don't have bugs this obvious. You appear to be misunderstanding what's > happening there. Those multipart parts appear to be properly formatted HTTP > requests. > > -- > sebastian > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
