Skip to content

Fix string type issues with SOAP/Twisted#685

Open
Neurones67 wants to merge 1 commit intoarskom:masterfrom
Neurones67:master
Open

Fix string type issues with SOAP/Twisted#685
Neurones67 wants to merge 1 commit intoarskom:masterfrom
Neurones67:master

Conversation

@Neurones67
Copy link
Copy Markdown

Fix some issues found when trying to use Twisted with SOAP protocol in Python3

@arskom-jenkins
Copy link
Copy Markdown

Can one of the admins verify this patch?

Comment thread spyne/protocol/soap/soap11.py

uri = _decode_path(request.uri)
return ''.join([url_scheme, "://", server_name, uri])
return ''.join([url_scheme, "://", server_name, uri.decode('utf-8')])
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we know that uri is encoded with utf-8 here?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought it was assumed as we create a "context" with utf-8 content type at line 676, but it concerns more the content than the headers.
The standard doesn't seem to allow other chars than ascii in URI during transmission, maybe it's better to decode as ascii rather than utf-8

Copy link
Copy Markdown
Member

@plq plq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the change in soap11.py is ok but i'm not sure about the other one.

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.

3 participants