András Veres-Szentkirályi

> I write golang, which doesn't have any third party http text parser at all and a partial stdib support. How about this? https://www.reddit.com/r/golang/comments/b5dtbh/comment/ejcrdbs/

> It only works with http1 Could you elaborate? What do you mean exactly by `http1`? Even when you enable HTTP headers, Piper will send textual representation of the HTTP...

Since that's only a string reference (as everything else is still text as in HTTP/1.1), I wouldn't care much about replacing it with a simple string replacing method/function. Also, if...

@sn00pyd0g3 both points are valid, although these could be solved in alternative ways, e.g. environment variables. Would that solve your particular problem(s) or do you also need what others mentioned...

It is possible, however, it will alter the request itself, which requires - parsing the request yet again before passing it to the script - serializing it after prepending the...

That's a better idea, thanks! I guess both should be opt-in, so how about an option like this: - do not pass host/port information (default) - pass host/port in faux...

It seems that threading this information - from the point where this metadata is still available - to the point where it can be passed into the extension is harder...

Unfortunately, no. Some cases can be avoided by passing the input via filename in a command line argument (as opposed to stdin), but this bug hasn't gotten much attention after...

Thanks, you found a weird combination of intended and unintended effects: - The protobuf models (which are also used for serializing the settings for automatic save/load) contain the `enabled` boolean...

> I prefer to use YAML (easier to read / edit / compare) and I would like to see the Prototobuf and YAML versions working in a same way. That...