From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.
Date: Wed, 09 Aug 2017 12:38:06 +0200 [thread overview]
Message-ID: <8760dxauwh.fsf@gmx.us> (raw)
In-Reply-To: 87a839awtd.fsf@gmx.us
Rasmus <rasmus@gmx.us> writes:
> Hi,
>
> Kaushal Modi <kaushal.modi@gmail.com> writes:
>
>> Thanks for checking. The validator (the default one in org-html-postamble)
>> never worked for me, probably because of something being blocked at work..
>> I get this when I click the validator link:
>>
>> =====
>> Sorry! This document cannot be checked.
>> No Referer header found!
>>
>> You have requested we check the referring page, but your browser did not
>> send the HTTP "Referer" header field. This can be for several reasons, but
>> most commonly it is because your browser does not know about this header,
>> has been configured not to send one, transferred the referring document
>> over a secure protocol such as https but is accessing the validator over
>> ordinary non-secure http, or is behind a proxy or firewall that strips it
>> out of the request before it reaches us.
>>
>> This is not an error in the referring page!
>> =====
>
> There’s definitely some sort of issue...
>
> I guess this is for a local file? I guess it needs to be publicly
> available. But it doesn’t seem to work all the time even for public
> pages.
>
> Using the following example, it only works from the http version, not the
> https version.
Https pages not working is a known "bug" cf.
https://validator.w3.org/docs/help.html#faq-referer
If a JS solution is OK, we could do something like this:
<a href="http://validator.w3.org/check?uri=referer"
onclick="this.href=
'https://validator.w3.org/check?uri='+encodeURIComponent(document.URL)">
Validate
</a>
This would work with public https pages if JS is supported. See:
https://validator.w3.org/favelets.html
https://lists.w3.org/Archives/Public/www-validator/2005Mar/0011.html
I have not found a way to send the raw source code via an url for local
files.
Rasmus
--
Dobbelt-A
next prev parent reply other threads:[~2017-08-09 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 17:35 Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export lists
2017-07-31 18:24 ` Kaushal Modi
2017-07-31 18:33 ` Kaushal Modi
2017-08-01 8:15 ` Nicolas Goaziou
2017-08-01 9:51 ` Rasmus
2017-08-01 10:41 ` Kaushal Modi
2017-08-01 11:18 ` Rasmus
2017-08-01 19:41 ` Kaushal Modi
2017-08-01 20:48 ` Rasmus
2017-08-01 20:59 ` Kaushal Modi
2017-08-09 9:56 ` Rasmus
2017-08-09 10:38 ` Rasmus [this message]
2017-08-14 20:15 ` Kaushal Modi
2017-08-01 22:03 ` Tim Cross
2017-08-01 21:58 ` Tim Cross
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760dxauwh.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).