(str/split
  "first=bla;second=foo;third=bar"
  #"[=;]+")

;; => ["first" "bla" "second" "foo" "third" "bar"]

You'll need to require clojure.string as str ofcourse

That might not work if some of the names and/or values can be enclosed in double quotes, with characters like = and/or ; inside the double quotes, if I am understand the original question correctly.

Right, that's the problem with a simple string split. The values can look like this "test\\=test=123;"

which would result in ["test=test" "123"] after parsing.

If done properly

It may be somewhat of a learning curve, perhaps, but you might want to take a look at a parsing library called .... thinking of the name

Instaparse: https://github.com/Engelberg/instaparse

It might make it easier to express what you want than figuring out a regex for it.

Oh I see

I know how to do this with loops, it's just a bit ugly and not clojure like.

I can revert to that if I need to, but just thought I'd ask for some advice here in case someone had an idea or approach that may be better.

I am almost certain it is possible to write a regex for that, but the amount of escaping inside the regex, combined with the escaping of the strings you are trying to recognize, would probably get a little bit mind-bending.

It might with Instaparse, too, not sure.

Clojure's data.csv library sounds like it has code to recognize at least similar, if not identical, escaping rules -- you may want to see if you can figure out how it does it: https://github.com/clojure/data.csv

For regex, I need it split on = where = is not preceded by \

and only split on the first one.

For regex, I would think a fully correct solution should recognize double-quoted strings, and all of the escaped things inside of them, until it finds the first non-escaped double-quote character after the leading double-quote character. Anything else is just asking for wrong corner cases.

Same idea if you use Instaparse

The CSV parser is helpful, they are using stringbuilders which is what I was going to use with loops.

I may be able to make something work in a similar way. Thanks for the help!

Assuming that a string like name="some value containing = character" is one name name, whose value is a string containing a non-escaped = character, which depending on the rules of your data format, may not require escaping if it is inside of double quotes.

Only = in the name portion are escaped, the value isn't as it's terminated by the ;

But I don't know if the string you are getting has any kind of spec for how it is formatted and ought to be parsed.

There is no written spec, I'm looking at code written in c# that is supposed to do this correctly. Hopefully it does 🙂

What about name="some string value containing ; and ="; ?

the quotes don't mean anything in this parser spec, so the ; inside the value would be escaped with a \ and only the final one would be used to indicate a new name value pair.

again, I don't know what all the rules are for your strings, but that is an example you may want to see whether it is considered legal to generate or not.

OK, then a warnings about looking at data.csv as an example: I am pretty sure that double quotes are special in CSV files.

So may not be as close to what you want as I originally thought it might be.

It gives me a direction, this should be a simpler task than the csv parser.

this isn't really a solution per se, but have you considered changing the protocol to something like JSON?

I don't control the protocol. I'm just writing a lowly client 🙂

What’s the error?

It seems it's not actually using the basic-auth middleware. It goes straight to the auth middleware function, resulting in 401 unauthorized.

Are they inserted in the right order? I believe Reitit uses the reverse order of Compojure.

@U0Y53Q0R4 reitit applies the middleware in the order defined, so it looks to be correct. There is a request debugging option, prints out all the applied mw, and how they have changed the request/response. Here's how to enable it: https://github.com/metosin/reitit/blob/master/examples/ring-swagger/src/example/server.clj#L67

hope this helps.

I discovered my problem was that I was passing the email and password parameters in the body, not in a header as buddy auth expected. Thanks for your help.