Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it clear that wwsympa_url needs to include the protocol #1115

Merged
merged 1 commit into from
Feb 16, 2021

Conversation

racke
Copy link
Contributor

@racke racke commented Feb 7, 2021

This prevents confusion seen at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929157#15
#876 (comment)

Even better to have a format that checks whether it is a valid URL.
E.g. by feeding it to the URI module and verify that all vital parts
are present.

This prevents confusion seen at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929157#15
sympa-community#876 (comment)

Even better to have a format that checks whether it is a valid URL.
E.g. by feeding it to the URI module and verify that all vital parts
are present.
@ikedas
Copy link
Member

ikedas commented Feb 8, 2021

This prevents confusion seen at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929157#15
#876 (comment)

I have read this bugreport and at the time felt good idea to omit schema in URL (it's a legitimate notation of relative URI reference: See RFC3986, 4.2). But now I know it's impossible.

This omission is useful in HTML source, because protocol of URLs may be taken from base URL the browser is accessing. However, it cannot apply to the parameter(s) of Sympa, because the server has to give the protocol used by itself.

Even better to have a format that checks whether it is a valid URL.
E.g. by feeding it to the URI module and verify that all vital parts
are present.

I agree.

@ikedas ikedas added this to the 6.2.62 milestone Feb 8, 2021
@ikedas ikedas merged commit 006af32 into sympa-community:sympa-6.2 Feb 16, 2021
@racke racke deleted the pr/wwsympa-url-confusion branch February 16, 2021 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants