You need to use a <br> because your Content-Type is text/html. It works without the Content-Type header because then your e-mail will be interpreted as plain text. If you really want to use \n you should use Content-Type: text/plain but then you’ll lose any markup. Also check out similar question here.
As seen in the documentation, from Django 1.8 there is a built in UUID field. The performance differences when using a UUID vs integer are negligible. import uuid from django.db import models class MyUUIDModel(models.Model): id = models.UUIDField(primary_key=True, default=uuid.uuid4, editable=False) You can also check this answer for more information.
RFC 7111 There is an RFC which covers it and says to use text/csv. This RFC updates RFC 4180. Excel Recently I discovered an explicit mimetype for Excel application/vnd.ms-excel. It was registered with IANA in ’96. Note the concerns raised about being at the mercy of the sender and having your machine violated. Media Type: … Read more
A probably easier approach would be to use Image.FromFile() and then use the RawFormat property, as it already knows about the magic bits in the headers for the most common formats, like this: Image i = Image.FromFile(“c:\\foo”); if (System.Drawing.Imaging.ImageFormat.Jpeg.Equals(i.RawFormat)) MessageBox.Show(“JPEG”); else if (System.Drawing.Imaging.ImageFormat.Gif.Equals(i.RawFormat)) MessageBox.Show(“GIF”); //Same for the rest of the formats
Content-Type: application/force-download means “I, the web server, am going to lie to you (the browser) about what this file is so that you will not treat it as a PDF/Word Document/MP3/whatever and prompt the user to save the mysterious file to disk instead”. It is a dirty hack that breaks horribly when the client doesn’t … Read more
According to the RFC 7231 section 3.1.5.5: A sender that generates a message containing a payload body SHOULD generate a Content-Type header field in that message unless the intended media type of the enclosed representation is unknown to the sender. If a Content-Type header field is not present, the recipient MAY either assume a media … Read more
You can find every content type here: http://www.iana.org/assignments/media-types/media-types.xhtml The most common type are: Type application application/java-archive application/EDI-X12 application/EDIFACT application/javascript application/octet-stream application/ogg application/pdf application/xhtml+xml application/x-shockwave-flash application/json application/ld+json application/xml application/zip application/x-www-form-urlencoded Type audio audio/mpeg audio/x-ms-wma audio/vnd.rn-realaudio audio/x-wav Type image image/gif image/jpeg image/png image/tiff image/vnd.microsoft.icon image/x-icon image/vnd.djvu image/svg+xml Type multipart multipart/mixed multipart/alternative multipart/related (using by MHTML (HTML mail).) … Read more
If you are posting JSON to Django, I think you want request.body (request.raw_post_data on Django < 1.4). This will give you the raw JSON data sent via the post. From there you can process it further. Here is an example using JavaScript, jQuery, jquery-json and Django. JavaScript: var myEvent = {id: calEvent.id, start: calEvent.start, end: … Read more
I am using this function, which includes several fallbacks to compensate for older versions of PHP or simply bad results: function getFileMimeType($file) { if (function_exists(‘finfo_file’)) { $finfo = finfo_open(FILEINFO_MIME_TYPE); $type = finfo_file($finfo, $file); finfo_close($finfo); } else { require_once ‘upgradephp/ext/mime.php’; $type = mime_content_type($file); } if (!$type || in_array($type, array(‘application/octet-stream’, ‘text/plain’))) { $secondOpinion = exec(‘file -b –mime-type … Read more
The first case is telling the web server that you are posting JSON data as in: {“Name”: “John Smith”, “Age”: 23} The second case is telling the web server that you will be encoding the parameters in the URL: Name=John+Smith&Age=23