Connor Prussin

This thread also brings up another interesting point, which is that currently HTTPure doesn't give you any escape hatches to resort back to low-level bindings for custom use cases or...

@paluh and I spoke offline to come up with a solution. He's going to put in a PR for the following changes: 1. We're going to split up the `RequestHeaders`...

@davezuch Unfortunately no, PRs welcome but in the meantime I haven't had a chance to work on this yet.

@rnons provided an example (see https://github.com/cprussin/purescript-httpure/issues/124); quoting here: > Hi, I'm trying to use httpure to write a simple backend. It's a bit strange when an error is > thrown,...

@akheron I would prefer to come up with some modification to the httpure api which forces users to handle uncaught exceptions in routes. I don't think there's a way to...

So what I had in mind was that we would just catch all exceptions and pass them off to a user-defined handler; so essentially we would force users to write...

I like the proposal to use a `Map String (Array String)`. I had wanted to convert it to a `Map String String` anyways, and I think that's a clean way...

Ok, those are good points, I've opened https://github.com/cprussin/purescript-httpure/issues/130 to track exposing the original request URL.

Yeah, I like that proposal. Let's split out a separate issue to track determining the right API to expose and implementing it

I am leaning towards following what Express does here, which is to ignore the empty `=`: ```js const express = require('express'); const app = express(); app.get('/', (req, res) => res.send(req.query));...