Releases: fracpete/requests4j
Releases · fracpete/requests4j
Release v0.1.6
- Added support for sending a payload with the
DELETE
method. Though this is not recommended by RFC 7231, section 4.3.5, other Python frameworks like requests and django support it
Release v0.1.5
- introduced
Resendable
interface, implemented by parameter, attachment and Request classes (NB: a stream parameter from anInputStream
cannot be resent) Request.canResend()
method returns whether the request can be resent again (eg if it fails due to outdated authentication headers)
Release v0.1.4
- parameters can also be
String[]
orjava.util.List
objects now, getting added to the URL multiple times
Release v0.1.3
- made it easier to post a single file or byte array via
Request.attachment(AbstractAttachment)
; adds aContent-Disposition
header withattachment
(byte array) orattachment; filename=NAME
(file)
requests4j-0.1.2
- now handles relative redirects properly
requests4j-0.1.1
- added support for missing
OPTIONS
method
requests4j-0.1.0
- swapped out underlying code, now using Apache's HttpClient
- separated
core
package intorequest
andresponse
- removed hostname verification support
requests4j-0.0.4
- added basic support for proxies in
Request
objects (proxy(...)
,noProxy()
)
requests4j-0.0.3
- the body of a
Request
can be eitherString
tobyte[]
now - added
add(Map<String,String>)
method toFormData
class (packagecom.github.fracpete.requests4j.form
)
requests4j-0.0.2
- introduced
HTTPResponse
interface (packagecom.github.fracpete.requests4j.core
) and the ability to supply a configuredHTTPResponse
object to theexecute
method, eg for streaming data rather than storing it in memory - new
HTTPResponse
classes in packagecom.github.fracpete.requests4j.core
:FileResponse
- writes received data straight to specified fileStreamResponse
- writes received data to providedjava.io.OutputStream