From: Max Nikulin <firstname.lastname@example.org>
Subject: Serving .org files for worg (was: Re: Library of babel help)
Date: Thu, 30 Jun 2022 22:45:11 +0700 [thread overview]
Message-ID: <email@example.com> (raw)
On 30/06/2022 16:06, Tim Cross wrote:
>> Aren't they currently available? I can and I was always able to get the
>> org sources by changing the link from .html to .org.
> No, that doesn't work for me using either chrome or firefox. Chrome just
> keeps switching back to the HTML url and firefox just hangs, returning
> nothing. Bastien has sent me the nginx config being used, but I've not
> yet had a look at it.
It is rather strange
curl -I 'https://orgmode.org/worg/doc.org'
browsers should offer "save as" dialog in such case. It is possible to
add Content-Disposition header to force "save" prompt, but I am unsure
if it the best option. I would prefer some desktop-wide MIME handler,
but there is not specific type for org. text/plain will be likely
handled by browsers internally. Unsure if something like "text/x-org" is
better since anyway custom configuration will be required.
Tim, did you face the problem with some particular file? Browsers might
try to guess real MIME type from file content. If the problem is
reproducible, you may experiment with "no sniff" header.
next prev parent reply other threads:[~2022-06-30 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 8:15 Library of babel help Tim Cross
2022-06-16 9:30 ` Tim Cross
2022-06-30 7:23 ` Ihor Radchenko
2022-06-30 9:06 ` Tim Cross
2022-06-30 13:25 ` Ihor Radchenko
2022-06-30 15:45 ` Max Nikulin [this message]
2022-06-30 17:04 ` Serving .org files for worg (was: Re: Library of babel help) Max Nikulin
2022-06-30 21:48 ` Tim Cross
2022-07-01 5:42 ` Max Nikulin
2022-07-29 13:10 ` Max Nikulin
2022-07-30 3:29 ` Tim Cross
2022-09-28 5:59 ` Serving .org files for worg Bastien
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).