Peter Fox

@RemiCollin little to none except it makes a much more clear structure for delivery. It separates the who, what and where into notifiable, notification and channel. You can easily do...

You should be able to fix this by looking at x-forwarded-port check if it doesn't match the internal server, for instance an SSL proxy will give 443 while the server...

I'm also having this issue, my guess it it's a permissions issue somewhere and not the library, but it's frustrating

Can confirm, fixed the problem for me.

There's no try catch statements or switch case statements... but +1 for getting this added