[
https://issues.apache.org/jira/browse/TIKA-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816095#comment-17816095
]
ASF GitHub Bot commented on TIKA-4188:
--------------------------------------
tballison opened a new pull request, #1587:
URL: https://github.com/apache/tika/pull/1587
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
Thanks for your contribution to [Apache Tika](https://tika.apache.org/)!
Your help is appreciated!
Before opening the pull request, please verify that
* there is an open issue on the [Tika issue
tracker](https://issues.apache.org/jira/projects/TIKA) which describes the
problem or the improvement. We cannot accept pull requests without an issue
because the change wouldn't be listed in the release notes.
* the issue ID (`TIKA-XXXX`)
- is referenced in the title of the pull request
- and placed in front of your commit messages surrounded by square
brackets (`[TIKA-XXXX] Issue or pull request title`)
* commits are squashed into a single one (or few commits for larger changes)
* Tika is successfully built and unit tests pass by running `mvn clean test`
* there should be no conflicts when merging the pull request branch into the
*recent* `main` branch. If there are conflicts, please try to rebase the pull
request branch on top of a freshly pulled `main` branch
* if you add new module that downstream users will depend upon add it to
relevant group in `tika-bom/pom.xml`.
We will be able to faster integrate your pull request if these conditions
are met. If you have any questions how to fix your problem or about using Tika
in general, please sign up for the [Tika mailing
list](http://tika.apache.org/mail-lists.html). Thanks!
> Add support for ARC files
> -------------------------
>
> Key: TIKA-4188
> URL: https://issues.apache.org/jira/browse/TIKA-4188
> Project: Tika
> Issue Type: Improvement
> Reporter: Gregory Lepore
> Priority: Minor
>
> The original version of the Internet Archive's storage format is the ARC
> format (later superseded by WARC and WACZ).
> The ARC (Archive) format is a file format used for storing web archives. It
> was developed by the Internet Archive to facilitate the mass storage of web
> pages, capturing the content as it appeared on the Internet at specific
> points in time. An ARC file is a single, large file that contains a sequence
> of archived web resources. Each entry in an ARC file includes the URL of the
> resource, the date it was captured, the HTTP response headers, and the
> content of the resource itself (such as HTML pages, images, and other media
> types).
> The structure of an ARC file generally consists of a file header followed by
> a series of records, each representing an individual web resource. The ARC
> file can be gzipped using a two step process where each record in the ARC
> file is gzipped, and then the entire file is gzipped.
> The original ARC format specification is here:
> [https://archive.org/web/researcher/ArcFileFormat.php]
> The WARC format is currently supported via jwarc, which also appears to have
> support for the ARC format (https://github.com/iipc/jwarc)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)