emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: Justin Silverman <jsilve24@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Error in html form of org manual [9.5.5 (9.5.5-ge58bd0 @ /home/jds6696/.emacs.d/straight/build/org/)]
Date: Tue, 25 Oct 2022 16:43:47 +0700	[thread overview]
Message-ID: <a8e91fe1-d980-c8a5-93f5-db29ccde1bc8@gmail.com> (raw)
In-Reply-To: <87r0yw4t92.fsf@gmail.com>

On 25/10/2022 07:54, Justin Silverman wrote:
> 
> Try going to this link:
> https://orgmode.org/manual/Images-in-LaTeX-export.html 
> 
> It just takes you to the Latex Export page. Most of the links on the 
> latex export page don't seem to go anywhere.

I expect that the problem was fixed some time ago. Perhaps your browser 
cached old response from the HTTP server.

curl -I https://orgmode.org/manual/Images-in-LaTeX-export.html
HTTP/1.1 200 OK
Server: nginx/1.14.2
Date: Tue, 25 Oct 2022 09:35:25 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 7418
Last-Modified: Sat, 15 Oct 2022 16:21:14 GMT
Connection: keep-alive
ETag: "634addfa-1cfa"
Accept-Ranges: bytes

Earlier it was 301 permanent redirection with the Location header. See 
the previous thread:

Bastien Guerry. Re: Some links in online manual do not work. Wed, 12 Oct 
2022 06:11:47 +0200. https//list.orgmode.org/87a661he9o.fsf@gnu.org

and the reason of server configuration changes caused the issue

Rudolf Adamkovič. [BUG] The documentation webserver gives 404s. Sun, 03 
Jul 2022 12:01:24 +0200. https://list.orgmode.org/m2sfni5xcb.fsf@me.com


      reply	other threads:[~2022-10-25  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25  0:54 [BUG] Error in html form of org manual [9.5.5 (9.5.5-ge58bd0 @ /home/jds6696/.emacs.d/straight/build/org/)] Justin Silverman
2022-10-25  9:43 ` Max Nikulin [this message]

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=a8e91fe1-d980-c8a5-93f5-db29ccde1bc8@gmail.com \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jsilve24@gmail.com \
    /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).