* origin/master:
fix line ending and indentation issues
AssignmentLevelSurtQueueAssignmentPolicy.java - Add support for forced queue assignment and parallel queues URIAuthorityBasedQueueAssignmentPolicy.java - Add interoperability between forced queue assignment and parallel queues QuotaEnforcer.java - Fix javadoc to match default behavior
Override PUT so it doesn't change the file extension
Use super.getVariants() rather than super.getVariants(GET)
Remove testConcurrentLoad
Mitigate random CookieStore.testConcurrentLoad test failures
Add missing UUID import (interactive commit fail)
Fix digest authentication
Link to javadoc.io for more recent api docs
Now jdk11 support is merged we can disallow test failures on it
Fix restlet child component context warning
Update statistics assertions as Jetty 9 produces different headers
Fix 'No session data store configured' test error
Drop support for JDK 7
JDK11: upgrade engine to jetty 9.4.19 and restlet 2.4.0
JDK11 support: upgrade jetty to 9.4.19 in modules tests
Prevent newer surefire from invoking FetchHTTPTests directly
JDK11 support: remove unused class ObjectIdentityBdbCache and tests
JDK11 support: exclude tools.jar from hbase-client dependency
JDK11 support: explicitly depend on JAXB
JDK11 support: upgrade maven-surefire-plugin to 2.22.2
Travis fixes
Update README and add LICENSE.txt
Fixes#268 ssl handshake_failure. Support for jdk11 was added in jetty
9.4.14 but we may as well bump to the latest stable version.
In Jetty 9 it appears the request is logged after the response is sent.
Thus it was racing with the assertions that check the client IP. So to
fix this rather stashing the 'lastRequest' we just make the server
echo the client's IP in a response header.
Some other minor tweaks were needed due to changes in Jetty behaviour:
- We stop checking the length of the raw response. It doesn't tell us
anything and easily varies.
- Jetty now generates Set-Cookie with a space after the ;
- Jetty now lowercases the word "basic" in WWW-Authenticate header
- testLaxUrlEncoding(): Jetty now rejects bad paths with a 400 error so
we disable the response checks. The actual request line is
still checked which is the important thing.
Note: This patch does not affect the version of jetty used by the
Heritrix admin console. That will be tackled separately.
* trough-dedup:
promote dirty segments at crawl finish
trough dedup!
Allow failed lookups to expire, for #234.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release 3.4.0-20190207
As @nlevitt suggestion, a further check.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release 3.4.0-20190205
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release 3.4.0-20190205-2
[maven-release-plugin] prepare for next development iteration
Extend to set additional property.
Use argument syntax.
Skip tests during release process (covered by CI).
Set consistent tag, and include contrib.
Wrong repo spec.
Add build profile for deployment to Maven Central.
Avoid headings being treated as lists
Clarification about APIs.
Swapped original and link to make maintenance simpler.
Tidy up markup and links.
Add synchronized statements for internetarchive/heritrix3#221.
Add checks to guard against server sending 304 in error, for #229.
do not checkpoint if crawl job has not started
* FetchHTTPTest.java
a bunch of new tests
* FetchHTTP.java
make sslTrustLevel work correctly (bug found by test; even with fix, only respects value at startup, no overrides)
* modules/pom.xml, .classpath
dependencies for testing
* engine/pom.xml
update jetty to 6.1.26 since we require that for the new tests
* **/pom.xml
bump version identifiers to "3.1.1-SNAPSHOT" (odd minor number meaning dev version, odd patch number indicating expected next patch number of 3.0.x release if before a 3.2.0 release)
* UURIFactoryTest.java
specify stirng literal with escape-encoding, rather than as raw UTF-8
* **/pom.xml
include 'project.build.sourceEncoding' property to suppress platform-encoding warnings
(unfortunately, neither this nor similar 'maven.compile.encoding' property actually casues maven build to interpret Java source as UTF-8)