openid / connect / issues / #91 - Basic -3.2.1 non-normative exapmle includes 2 white spaces which are not encoded — Bitbucket

Issue #91 resolved

Former user created an issue 2011-09-14

If we use GET & query string to specify parameters, white space should be encoded.

response_type=token id_token ... scope=openid profile

->

response_type=token%20id_token ... scope=openid%20profile

Comments (3)

Former user Account Deleted
- changed title to Basic - non-normative exapmle includes 2 white spaces which are not encoded
- 2011-09-14T21:51:05+00:00
Former user Account Deleted
- changed title to Basic -3.2.1 non-normative exapmle includes 2 white spaces which are not encoded
- 2011-09-14T21:51:25+00:00
Edmund Jay
- changed status to resolved
fixes ~~#91~~

→ 1528b0b892b6
- 2011-09-17T01:44:01+00:00
Log in to comment

Assignee: –

Type: bug

Priority: major

Status: resolved

Component: –

Milestone: –

Version: –

Votes: 0

Watchers: 0

Jira: the preferred issue tracker for Bitbucket. Join the team!