public class EepHead extends EepGet
EepHead foo = new EepHead(...);
if (foo.fetch()) {
String lastmod = foo.getLastModified();
if (lastmod != null) {
parse the string...
...
}
}
Other use cases (command line, listeners, etc...) lightly- or un-tested.
Note that this follows redirects! This may not be what you want or expect.
Writing from scratch rather than extending EepGet would maybe have been less bloated memory-wise.
This way gets us redirect handling, among other benefits.EepGet.AUTH_MODE, EepGet.AuthState, EepGet.CLIStatusListener, EepGet.Gunzipper, EepGet.StatusListener_aborted, _acceptRanges, _actualURL, _alreadyTransferred, _authState, _bytesRemaining, _bytesTransferred, _cacheControl, _contentEncoding, _contentLanguage, _contentType, _context, _cookie, _csp, _currentAttempt, _decompressException, _encodingChunked, _etag, _etagOrig, _expiryDate, _extraHeaders, _fetchHeaderTimeout, _fetchInactivityTimeout, _fetchTotalTimeout, _isGzippedResponse, _keepFetching, _lastModified, _lastModifiedOrig, _listeners, _log, _notModified, _numRetries, _out, _outputFile, _outputStream, _proxy, _proxyHost, _proxyIn, _proxyOut, _proxyPort, _redirectLocation, _redirects, _referrerPolicy, _responseCode, _responseText, _server, _shouldProxy, _shouldWriteErrorToOutput, _status, _transferEncoding, _transferFailed, _url, _vary, _xContentTypeOptions, _xframeOptions, _xPoweredBy, _xssProtection, CONNECT_TIMEOUT, INACTIVITY_TIMEOUT, MAX_COMPLETE_FAILS, USER_AGENT| Constructor and Description |
|---|
EepHead(I2PAppContext ctx,
String proxyHost,
int proxyPort,
int numRetries,
String url) |
| Modifier and Type | Method and Description |
|---|---|
protected void |
doFetch(SocketTimeout timeout)
This reads the response to a single fetch.
|
long |
getContentLength()
We don't decrement the variable (unlike in EepGet), so this is valid
|
protected String |
getRequest() |
static void |
main(String[] args)
EepHead [-p 127.0.0.1:4444] [-n #retries] url
This doesn't really do much since it doesn't register a listener.
|
protected boolean |
shouldReadBody()
Should we read the body of the response?
|
addAuthorization, addHeader, addStatusListener, fetch, fetch, fetch, getAcceptRanges, getCacheControl, getContentEncoding, getContentLanguage, getContentType, getCookie, getCSP, getEtag, getExpiryDate, getLastModified, getNotModified, getReferrerPolicy, getServer, getStatus, getStatusCode, getStatusText, getTransferEncoding, getVary, getXContentTypeOptions, getXframeOptions, getXPoweredBy, getXSSProtection, parseAuthArgs, readChunkLength, readHeaders, sendRequest, setPostData, setPostData, setPostData, setWriteErrorToOutput, stopFetching, suggestNamepublic EepHead(I2PAppContext ctx, String proxyHost, int proxyPort, int numRetries, String url)
protected void doFetch(SocketTimeout timeout) throws IOException
EepGetdoFetch in class EepGettimeout - may be null as of 0.9.49IOExceptionpublic long getContentLength()
protected String getRequest() throws IOException
getRequest in class EepGetIOExceptionpublic static void main(String[] args)
protected boolean shouldReadBody()
shouldReadBody in class EepGet