From: mails.lists.2012-1-rRloVJBGZzogAv4oPwG0Al6hYfS7NtTn@public.gmane.org
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Unexpected behaviour with pandoc-server
Date: Sat, 1 Apr 2023 23:27:01 +0200 [thread overview]
Message-ID: <a84dc893-f23f-8468-5d3a-4af15d73ac2c@ohrner.net> (raw)
Hi all,
I tried out pandoc 3.1.2 server, installed as a CGI script for Apache on
Debian 11 "Bullseye" x64.
(I first planned to run pandoc-server in actual server mode to avoid the
CGI start overhead, but could not figure out how to configure it to
listen to localhost only - is this possible?)
I used it for Jira Markup -> gfm conversion, and it worked quite fine,
except for one specific jira rich text content I encountered.
This content formats just fine without any noticeable delay with
pandoc -f jira -t gfm --sandbox --wrap=preserve < in.jira > out.md
on my local machine.
The server with its default settings first (reproducibly) returned 503
errors for this content, though.
When I increased the timeout to 10 seconds, a successful reply was
returned - after a considerable delay - but the text was basically
unconverted. Markdown specific special chars were escaped actually, but
Jira formatting like {code} was left unmodified in the text.
This completely differs from CLI pandoc invocation, which properly
converts these formattings immediately, without any noticable delay.
Is this to be expected and what's the background?
Or am I encountering a possible bug I should try to analyze further (at
least the behaviour, probably not the pandoc code...)?
Unfortunately, I cannot simply share the Jira snipped here, so if it's
of interest I need to try to condense it into a minimal test case.
Of course I may also be doing wrong when sending the request (I'm
sending all arguments as JSON as documented, and only accept JSON for a
reply - this works fine in all other cases I tested, though, and
conversion is much quicker than for this single "strange" Jira field).
My intermediate solution was to just build a minimal CGI shell script
which in turn just uses pandoc in command line pipe mode - this also
works fine and fast, so it's unrelated to the server machine and the
pandoc binary installed on it.
Best regards,
Gunter
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a84dc893-f23f-8468-5d3a-4af15d73ac2c%40ohrner.net.
next reply other threads:[~2023-04-01 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 21:27 mails.lists.2012-1-rRloVJBGZzogAv4oPwG0Al6hYfS7NtTn [this message]
[not found] ` <a84dc893-f23f-8468-5d3a-4af15d73ac2c-8DM0qNeCP8OsTnJN9+BGXg@public.gmane.org>
2023-04-02 8:11 ` Albert Krewinkel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a84dc893-f23f-8468-5d3a-4af15d73ac2c@ohrner.net \
--to=mails.lists.2012-1-rrlovjbgzzogav4opwg0al6hyfs7nttn@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).