Michael Hart

@moll can you give me an example of what you're talking about? Fetch uses a completely different options API to Node.js – doesn't it rely on the [`Headers`](https://developer.mozilla.org/en-US/docs/Web/API/Headers) interface for...

Sorry, I'm still confused – can you show me that actual Fetch code you're using? Using `for ... in ...` definitely won't give you what you want: ```js var myHeaders...

Hmmm, not too sure about this – why were you adding ports in the first place, if they're just standard ports?

@brnkrygs well I'm not sure whether it's best to mess with the port handling or just add it to documentation – I'll probably need to do some testing in non-Node.js...

(to clarify: not remove them as an option – just remove the property from the `options` object if it happens to be a default port – so you can pass...

Hmmm, bit of a snag – what if someone wants to use `443` with `http`, or `80` with `https`?

@brnkrygs but Node.js knows whether you're sending http or https because of the module you use – not the options

@Dayjo the title was misleading – API Gateway has been supported by `aws4` since it launched – it just expects you to pass in a `host` and `path` as per...

@Dayjo what does your code look like?

@Dayjo - yeah, I see a bunch of things. Firstly, the `uri` is not supported (already covered this obvs) – use `host` and `path` instead. Secondly, you shouldn't modify the...