yacy/startYACY.bat, branch masterYaCy search server with some extra patches
https://git.fennell.dev/yacy/atom?h=master2026-07-10T20:47:39ZWe migrate to JDK 172026-07-10T20:47:39ZMichael Peter Christenmc@yacy.net2026-07-10T20:47:39Zurn:sha1:dd0225bdde303cc739fed60c9aff28b63b868997
This is a hard requirement to be able to migrate
to a more recent jetty version, which may happen sometime soon.fixed windows installer; updated download path for java installer2026-01-01T22:58:10ZMichael Peter Christenmc@yacy.net2026-01-01T22:58:10Zurn:sha1:3ecb0b459ee8500aa721b4ee8804bbde6f5c9dc3for some strange reason there is no javaw in temurin, only java2022-10-05T22:11:04ZMichael Peter Christenmc@yacy.net2022-10-05T22:11:04Zurn:sha1:32e6a5f9037dce684853cf358988f59215072ef7removed Xms java memory startup parameter2021-07-19T18:04:11ZMichael Peter Christenmc@yacy.net2021-07-19T18:04:11Zurn:sha1:15b7461bc7968bcfd8dfc516cf91c3548195e4a3
We will use the default value for now on.
This is much better for resource economy and fits better into a
container/docker/kubernetes strategy.
Furthermore, a small memory footprint is essential for the usage on
small devices like RaspberryPi.Made SNI extension user configurable without the need for server restart2019-04-14T13:41:13Zlucciomanluccioman@users.noreply.github.com2019-04-14T13:41:13Zurn:sha1:a5771b1f147b2a6f541b58ea832c86a85d92ab70
TLS Server Name Indication (SNI) extension activation can now be
configured with the new Settings_p.html?page=httpClient administration
page.
SNI extension is also now enabled by default, as in 2019 the
unrecognized_name(112) alert is more properly handled by major web
servers TLS implementations, following the RFC 6066 standard.
Related YaCy issues : #153 #189 and #272
JDK 1.7 bug :
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=7127374
Apache httpd issue :
https://bz.apache.org/bugzilla/show_bug.cgi?id=56241
RFC 6066 : https://tools.ietf.org/html/rfc6066#section-3upd classpath in batches (remove not necessary htroot)2016-02-03T20:50:50Zregerreger18@arcor.de2016-02-03T20:50:50Zurn:sha1:375d49d53667b3aeb8efc8eb9af7085058080796
see prev commitmove java environment parameter setting disabling SNI (Server Name Indicator) support for https connections from code to startup script allowing admin to ~easy/transparent alter the YaCy default FALSE setting.2015-07-29T21:30:05Zregerreger18@arcor.de2015-07-29T21:30:05Zurn:sha1:2fb6ebe88a6eb3d0bf565e212abf79c71da37ae2
Background: some user report problem with connecting/crawling some sites via https which require SNI support (by default switched off in YaCy). On the other hand systems not demanding SNI support are sometimes not properly configured and due to a bug/feature in java 1.7 connection is aborted. The later is more often the case, so the default is still fine. With the java start parameter expert user can no alter the startparameter to -Djsse.enableSNIExtension=true (java default) if they crawl more hosts requiring SNI support.
The alternative to let YaCy try both during https handshake (deep inside the httpclient) is not pursut at this time.add a -config command line parameter e.g. -config "port=9090" "port.ssl=8043"2014-02-24T04:16:31Zregerreger18@arcor.de2014-02-24T04:16:31Zurn:sha1:a9b06f87190fc9f94a7a2dbafc32c30766062f24
- useful for remote installation to set any config file property
- multipe parameter can be set at once, on Windows enclose parameter in doublequotes
- special handling "adminAccount=adminuser:adminpwd" sets adminusername and md5 encoded admin-pwd
- adjusted windows startbatch to allow command line parameter handling
- remove not needed classpath calculation from startYACY_debug.batchanged start parameters which caused deadlocks in mac and windows2013-12-04T23:55:35ZMichael Peter Christenmc@yacy.net2013-12-04T23:55:35Zurn:sha1:f722e450b308b859a2cd17db0e5991fddb8fbf58
versionsreverted start script options - yacy on windows did not start with the2013-07-27T13:36:46Zorbitermc@yacy.net2013-07-27T13:36:46Zurn:sha1:f117ea0492ea8a3e6b35fe783c9aa0043e88c9d8
given values