Key | Value |
---|---|
FileName | ./usr/share/maven-poms/httpcomponents/httpcomponents-core.pom |
FileSize | 9876 |
MD5 | 6A653126F7680BDA499E689323C249AB |
SHA-1 | 036430182037DDD394DEECD8BE74C9C047AFDB96 |
SHA-256 | F1050BCEE478AA79A7220325871789DA8CBF9ECE249CF62A6F0A51AB335ECB71 |
SSDEEP | 192:e9VHU79t9rHAbpQwa5ErreugQjQAIM9lVgbA0mE7M6m1ccXmMu21hjvGbv9:e9m7bFHZwa2eugwcs9yM6m1ccXmM7PY1 |
TLSH | T18F1212B198FC44B223C60AC28F225586FFB6C2EBE0459148F19C97506F5EFCE82E7556 |
hashlookup:parent-total | 2 |
hashlookup:trust | 60 |
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 7B79270DFC02F7F7ED2A4EA260017384 |
PackageArch | noarch |
PackageDescription | HttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner. |
PackageMaintainer | Fedora Project |
PackageName | httpcomponents-core |
PackageRelease | 2.fc24 |
PackageVersion | 4.4.4 |
SHA-1 | 395C678A3580233A779BDAFB98C51238992ADC71 |
SHA-256 | 1866D4EA6DE080FE040DC7F1F79335523429595E05217547699C61BB1D14114C |
Key | Value |
---|---|
MD5 | 183D3888BA13C60DD7E30284E7AFCC20 |
PackageArch | noarch |
PackageDescription | HttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner. |
PackageMaintainer | Fedora Project |
PackageName | httpcomponents-core |
PackageRelease | 2.fc24 |
PackageVersion | 4.4.4 |
SHA-1 | 80F3BC80852E79B5B38A13E52365D9CAB0B846F2 |
SHA-256 | 00356159C70ABC1557F2A1595F1682AF1A983D96A1A45DC4C804AE10AA4B7B6C |