<feed xmlns='http://www.w3.org/2005/Atom'>
<title>yacy/bin/protectedPostApiCall.sh, branch master</title>
<subtitle>YaCy search server with some extra patches
</subtitle>
<id>https://git.fennell.dev/yacy/atom?h=master</id>
<link rel='self' href='https://git.fennell.dev/yacy/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.fennell.dev/yacy/'/>
<updated>2018-11-27T10:36:40Z</updated>
<entry>
<title>Also check yacy.conf file existence in shell scripts where relevant</title>
<updated>2018-11-27T10:36:40Z</updated>
<author>
<name>luccioman</name>
<email>luccioman@users.noreply.github.com</email>
</author>
<published>2018-11-27T10:36:40Z</published>
<link rel='alternate' type='text/html' href='https://git.fennell.dev/yacy/commit/?id=106bfd0e5f7cc9cabf32a5c2110db44e9200bdd3'/>
<id>urn:sha1:106bfd0e5f7cc9cabf32a5c2110db44e9200bdd3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Added support for custom DATA path in shell scripts</title>
<updated>2018-11-26T17:26:52Z</updated>
<author>
<name>luccioman</name>
<email>luccioman@users.noreply.github.com</email>
</author>
<published>2018-11-26T17:26:52Z</published>
<link rel='alternate' type='text/html' href='https://git.fennell.dev/yacy/commit/?id=17ad1f7e65475f6f5de96f69e74c938fac699768'/>
<id>urn:sha1:17ad1f7e65475f6f5de96f69e74c938fac699768</id>
<content type='text'>
When the YACY_DATA_PATH environment variable is set, shell scripts will
now use the given path instead of relative ../DATA which remains the
default when the variable is not set.

Necessary in the context of Snap package (see issue #254) as YaCy is
started with startYACY.sh and an absolute DATA parent path in parameter.</content>
</entry>
<entry>
<title>Enforced access controls on some administrative actions.</title>
<updated>2017-03-26T09:48:00Z</updated>
<author>
<name>luccioman</name>
<email>luccioman@users.noreply.github.com</email>
</author>
<published>2017-03-26T09:48:00Z</published>
<link rel='alternate' type='text/html' href='https://git.fennell.dev/yacy/commit/?id=cde237b68763c542da20038e5f62bea341ae1d37'/>
<id>urn:sha1:cde237b68763c542da20038e5f62bea341ae1d37</id>
<content type='text'>
 - ensure use of HTTP POST method : HTTP GET should only be used for
information retrieval and not to perform server side effect operations
(see HTTP standard https://tools.ietf.org/html/rfc7231#section-4.2.1)
 - a transaction token is now required for these administrative form
submissions to ensure the request can not be included in an external
site and performed silently/by mistake by the user browser</content>
</entry>
</feed>
