Fork me on GitHub
#yada
<
2016-11-16
>
tcoupland14:11:23

do you think my PR might get love or not today? Appreciate I went for the PR->convo route, rather than the convo->PR route with it, and everyone's busy, would like to avoid having to push a 'special' version to somewhere is all.

peterwestmacott14:11:53

Is there any danger in returning stack traces on for example a 403?

imre14:11:57

if it's a public facing api I don't like to expose any stack info whatsoever

peterwestmacott15:11:30

Are there specific bad things that can happen, and if so can I hide/disable it in yada?

peterwestmacott15:11:04

ah - found a page in the manual to turn them off!

imre15:11:32

can you share the url? I haven't seen that page yet

peterwestmacott15:11:56

sure: https://juxt.pro/yada/manual/index.html and then ctrl+f for “stack trace"

imre15:11:14

pwned lol

imre15:11:16

turns out that's roughly what I use:

imre15:11:21

(set (range 401 500)) {:produces produced-media-types
                                             :response (constantly "")}

imre15:11:47

I thought there was a more idiomatic way

peterwestmacott16:11:48

I’m borrowing that set/range combo...