timothee-haudebourg/iref

Issues

• Incorrect extraction of URI components

  #21 opened 9 months ago by yescallop
  2

• Infinite loop in `parse::find_port`

  #20 opened a year ago by xiaozhiyan
  2

• BStr?

  #19 opened a year ago by Longor1996
  4

• "//1.1.1.1a", "//1.1.1.1111" & "//[1::]" misinterpreted to have invalid path

  #15 opened a year ago by yescallop
  5

• More compact `ParsedIriRef`.

  #10 opened a year ago by timothee-haudebourg
  2

• Panic in parse_ipv6_literal()

  #16 opened 2 years ago by eikendev
  1

• IRI reference resolution wrongly adds a `./` at the start of the path.

  #14 opened 3 years ago by timothee-haudebourg
  0

• Invalid IRI reference resolution when the base IRI path ends with `.`

  #13 opened 3 years ago by timothee-haudebourg
  0

• `#` character wrongly accepted in fragment part.

  #12 opened 3 years ago by timothee-haudebourg
  1

• Use `slice-dst` until custom DSTs land

  #9 opened 4 years ago by MattesWhite
  10

• More documentation

  #1 opened 5 years ago by timothee-haudebourg
  0

• Implement convenience traits

  #6 opened 4 years ago by MattesWhite
  1

• Implement AsRef for IriBuf to Iri

  #4 opened 4 years ago by bbqsrc
  3

• Spaces are accepted by the parser

  #2 opened 5 years ago by timothee-haudebourg
  0