Previously, a Zip64 jar file was identified by the number of entries
in the central directory being 0xFFFF. This value indicates that
there the number of entries is too big for the 2-byte field. However,
a jar may be in Zip64 format due to it exceeding the Zip format's
maximum size rather than its maximum number of entries so this field
cannot be used as a reliable indicator. The Zip specification doesn't
require any of the fields of the end of central directory record to
have a value of 0xFFFF (2-byte fields) or 0xFFFFFFFF (4-byte fields)
when using Zip64 format so we need to take a different approach.
Additionally, a number of places in the code assumed that an entry's
offset would always be available from the central directory file
header directly. This assumption did not hold true when the jar was
a Zip64 archive due to its size as the offset's value would be
0xFFFFFFF indicating that it should be read from the Zip64 extended
information field within the header's extra field instead.
This commit updates the Zip64 detection to look for the Zip64 end of
central directory locator instead. If present, it begins 20 bytes
before the beginning of the end of central directory record. Its
first four bytes are always 0x07064b50. The code that reads the
local header offset has also been updated to refer to the Zip64
extended information field when the offset is too large to fit in
the 4-byte field in the central directory file header. To allow
greater-than-4-byte offsets to be handled, a number of fields,
method parameters, and local variables have had their type changed
from an int to a long.
Fixes gh-27822
* pr/27759:
Make editorial changes to actuator documentation
Update actuator docs to prefer "You can..."
Improve actuator example lead-in text
Polish actuator docs markup and formatting
Closes gh-27759
Edit the actuator docs so that more "You can..." phrasing is used.
For example
"Auditing can be enabled by providing"
becomes
"You can enable auditing by providing"
See gh-27759
Update example lead-in text to a slightly shorter form.
For example
"as shown in the following example"
Becomes
"as the following example shows"
See gh-27759
This commit reworks the configuration properties registrar to use
RootBeanDefinition and a standard attribute rather than relying on
a package private sub-class. This allows other components to inspect
the metadata if necessary.
Closes gh-27821
Andy Wilkinson
Phillip Webb
Jay Bryant
Madhura Bhave
Stephane Nicoll
Kirill Gavrilov
dreis2211
Julien Dubois
Vladimir Konkov
Yanming Zhou
izeye