Line | |
---|
1 | <message> |
---|
2 | <header> |
---|
3 | <field> |
---|
4 | Content-Type: multipart/mixed; boundary="boundary"</field> |
---|
5 | </header> |
---|
6 | <multipart> |
---|
7 | <preamble> |
---|
8 | preamble |
---|
9 | </preamble> |
---|
10 | <body-part> |
---|
11 | <header> |
---|
12 | <field> |
---|
13 | Content-Type: text/plain</field> |
---|
14 | </header> |
---|
15 | <body> |
---|
16 | first part |
---|
17 | </body> |
---|
18 | </body-part> |
---|
19 | <body-part> |
---|
20 | <header> |
---|
21 | <field> |
---|
22 | Content-Type: text/plain</field> |
---|
23 | </header> |
---|
24 | <body> |
---|
25 | from the rfc: |
---|
26 | ================================ |
---|
27 | encapsulation := delimiter transport-padding |
---|
28 | CRLF body-part |
---|
29 | ================================ |
---|
30 | and also |
---|
31 | ================================ |
---|
32 | "Composers MUST NOT generate non-zero length transport |
---|
33 | padding, but receivers MUST be able to handle padding |
---|
34 | added by message transports." |
---|
35 | ================================ |
---|
36 | |
---|
37 | second part have a start boundary ending with spaces |
---|
38 | and also have a boundary not at the beginning |
---|
39 | --boundary |
---|
40 | ... that should be ignored |
---|
41 | |
---|
42 | also a boundary with more data (a tab) shoud be ignored |
---|
43 | --boundary |
---|
44 | |
---|
45 | end of part |
---|
46 | </body> |
---|
47 | </body-part> |
---|
48 | <epilogue> |
---|
49 | epilouge</epilogue> |
---|
50 | </multipart> |
---|
51 | </message> |
---|
Note: See
TracBrowser
for help on using the repository browser.