Alan Plum

@hallicarnassus that's not really the same thing, though. You're literally serving the files as part of your service whereas the README is served by ArangoDB itself. Your workaround also requires...

@hallicarnassus hardcoding database and mount paths into the service is a pretty bad idea. These should be considered implementation details. You might want the same service installed in multiple databases,...

Totally agree. We're already supporting many node modules. Currently the biggest difference are the I/O (i.e. fs/http/https/tcp) modules and the crypto module, for which we provide our own implementations. It...

@Simran-B The request module only uses the `internal.download` under the hood and doesn't do any special handling of these itself. I would assume that function probably doesn't expect headers to...

I think `internal.download` might not support multiple headers with the same name. This should be considered a bug with `internal.download` I think. @joerg84 Any idea who might be able to...

@dothebart can you clarify why? Multiple headers with the same name is pretty normal in HTTP. It should be possible to provide a backwards-compatible API by exposing the full headers...

This is for talking to other (third-party) servers, not ArangoDB. Does Fuerte work there too?

Clarified via Slack: Fuerte will also support http/http2 and replace all use cases of `internal.download`.

Without knowing what `newInterest` looks like it's difficult to tell, but the error message indicates ArangoDB doesn't like a document key, so this is likely a missing or invalid `_from`...

~~I ran into the same issue when importing typefaces locally in CRA with TypeScript (not sure if that detail is important). The bundle in the browser doesn't seem to include...