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
We initially had some trouble decoding and parsing the RidgeTec emails because they were in an encoding called "Quoted-Printable Content-Transfer-Encoding" (see Stack Overflow post about it here). We've since successfully decoded it, and the HTML body Looks clean, but the headers appear to still be stuck in that same form of encoding. Perhaps the headers had an additional layer of nested encoding?
At any rate, we are able to extract the thumbnail URL and metadata just fine, so I suppose this isn't terribly high priority.
The text was updated successfully, but these errors were encountered:
We initially had some trouble decoding and parsing the RidgeTec emails because they were in an encoding called "Quoted-Printable Content-Transfer-Encoding" (see Stack Overflow post about it here). We've since successfully decoded it, and the HTML body Looks clean, but the headers appear to still be stuck in that same form of encoding. Perhaps the headers had an additional layer of nested encoding?
At any rate, we are able to extract the thumbnail URL and metadata just fine, so I suppose this isn't terribly high priority.
The text was updated successfully, but these errors were encountered: