URI.js changelog

Changelog History

Page 1

• v1.19.7 Changes

  July 14, 2021

  • 🔒 SECURITY fixing URI.parseQuery() to prevent overwriting __proto__ in parseQuery() - disclosed privately by @NewEraCracker
  • 🔒 SECURITY fixing URI.parse() to handle variable amounts of \ and / in scheme delimiter as Node and Browsers do - disclosed privately by ready-research via https://huntr.dev/
  • ✂ removed obsolete build tools
  • ⚡️ updated jQuery versions (verifying compatibility with 1.12.4, 2.2.4, 3.6.0)

• v1.19.6 Changes

  February 13, 2021

  • 🔒 SECURITY fixing URI.parse() to rewrite \ in scheme delimiter to / as Node and Browsers do - disclosed privately by Yaniv Nizry from the CxSCA AppSec team at Checkmarx

• v1.19.5 Changes

  December 30, 2020

  • ⬇️ dropping jquery.URI.js from minified bundle accidentally added since v1.19.3 - Issue #404

• v1.19.4 Changes

  December 23, 2020

  • 🔒 SECURITY fixing URI.parseAuthority() to rewrite \ to / as Node and Browsers do - followed up to by alesandroortiz in PR #403, relates to Issue #233

• v1.19.3 Changes

  December 20, 2020

  • 🔒 SECURITY fixing URI.parseAuthority() to rewrite \ to / as Node and Browsers do - disclosed privately by alesandroortiz, relates to Issue #233

• v1.19.2 Changes

  October 20, 2019

  • 🛠 fixing URI.build() to properly handle relative paths when a scheme is given - Issue #387
  • 🛠 fixing URI.buildQuery() to properly handle empty param name - Issue #243, PR #383
  • 👌 support Composer PR #386

• v1.19.1 Changes

  February 10, 2018

  • 🛠 fixing .href() to parse query property - Issue #366, PR #367

• v1.19.0 Changes

  October 01, 2017

  • ➕ adding .setFragment() to query fragment plugin - Issue #338, PR #356
  • ➕ adding setting URI.preventInvalidHostname to control if an error should be thrown on invalid input - Issue #352, Issue #354, Issue #355 - effectively making the changes of version 1.18.11 opt-in rather than default.

• v1.18.12 Changes

  August 10, 2017

  • 📜 making URI.parse() allow _ in hostname - Issue #347, PR #348
  • 🛠 fixing URI.parse() to not use Number.isNumber() for IE compatibility - Issue #350, PR #351

• v1.18.11 Changes

  August 08, 2017

  • 📜 making URI.parse() throw on invalid port and hostname - Issue #344, PR #345

• 1
• 2
• 3
• 4
• 5
• Next ›
• Last »