WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@benoitc
Copy link
Owner

@benoitc benoitc commented Aug 21, 2020

Current way to pass the socket requires the user to url encode the path.
For example /var/run/mysocketshould be encoded as
%2Fvar%2Frun%2Fmyscoket which is not really convenient.

Changes:

We introduce thiss tuple as a ne format {<<"unix:/var/run/mysock'>>,<<"http://path/to/resource"> }

This allows the user to pass a path withut encoding it while supporting
extensions in the future.

note: for now only http is suppored.

Current way to pass the socket requires the user to url encode the path.
For example "/var/run/mysocket' should be encoded as
"%2Fvar%2Frun%2Fmyscoket" which is not really convenient.

Changes:

We introduce thiss tuple as a ne format {<<"unix:/var/run/mysock'>>,
<<"http://path/to/resource"> }

This allows the user to pass a path withut encoding it while supporting
extensions in the future.

note: for now only http is suppored.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants