Skip to content

Releases: Zelak312/flaresolverr-mitm-proxy

v1.0.5

13 Oct 23:30
Compare
Choose a tag to compare

Miscellaneous Tasks

  • Bumping git-cliff to v2 (39c946b)
  • Update deps to fix issues + add test cmd for quick testing (5b68a0c)

Chore

  • Bump cryptography from 42.0.7 to 43.0.1 (ccffd8f)

v1.0.4

06 Aug 14:32
Compare
Choose a tag to compare

Miscellaneous Tasks

  • Remove skip for some commit messages in cliff (625698f)

Chore

  • Bump certifi from 2023.7.22 to 2024.7.4 (6192244)
  • Bump tornado from 6.3.3 to 6.4.1 (f95a6f4)
  • Bump zipp from 3.16.2 to 3.19.1 (3b836cb)

v1.0.3

07 May 22:28
Compare
Choose a tag to compare

Bug Fixes

  • Issues with requested library versions (918ea77)

Miscellaneous Tasks

  • Remove "example.addon" head comment (#14) (8c50c78)
  • Return headers[] in url flaresolver response (#15) (48ac632)
  • Remove logging (0ab5638)

v1.0.2

13 Jan 23:42
Compare
Choose a tag to compare

Features

Miscellaneous Tasks

  • Change example docker-compose to use latest version (a7c54cc)

v1.0.1

10 Jan 01:51
Compare
Choose a tag to compare

Bug Fixes

  • Auth for upstream proxy needs to be passed in an other parameter of mitmdump (24281e8)

v1.0.0

22 Dec 21:34
Compare
Choose a tag to compare

Bug Fixes

  • Proxy configuration and doc (a8bc206)
  • Curl example command so it's pastable in cli (155f524)

Features

Miscellaneous Tasks

  • How to send cookies (e0737ec)
  • Adding buy me a coffee link (2313fb6)
  • Move platforms to build for (b99f359)

v1.0.1-beta

28 Nov 13:49
Compare
Choose a tag to compare
v1.0.1-beta Pre-release
Pre-release

v1.0.1-beta

Breaking changes:

  • Headers for post requests are not longer in postData but are also in the query (same as GET queries)
  • JSON post data is now sent using a JSON base64 encoded string
  • The Post and Header special tokens changed to $$headers[] and $$post

Fixes:

  • Fixed problem in GET queries headers not being applied correctly

Features:

  • Being able to change the spceial tokens prefix and header split token as well
  • Being able to pass in a real JSON which now retains the type as well so numbers and other JSON accepted types now work ex: {"test": 4} before 4 would have been considered a string