You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The second bug is in WASwazooAdaptor>>requestUrlFor:. In this case WAUrl is fed
the printString of the #uri (an instance of SwazooURI) as follows:
requestUrlFor: aNativeRequest
| url |
url := ((WAUrl absolute: aNativeRequest uri printString)
decodedWith: self codec).
aNativeRequest isEncrypted
ifTrue: [ url scheme: 'https' ].
^ url
The problem occurs because WAUrl class>>absolute: expects the url to be url
encoded, but the printString for SwazooURI prints the decoded url. Again this
causes problems when HTTP special characters are in the input url. The other
adaptors feed the 'raw' encoded url string to WAUrl, but the Swazoo adaptor
does not ... SwazooURI does not keep the encoded source url around, so in my
workaround I changed SwazooURI printQueriesOn: to reencode the query parameters
...
Original issue reported on code.google.com by philippe...@gmail.com on 6 Aug 2011 at 7:10
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
philippe...@gmail.com
on 6 Aug 2011 at 7:10The text was updated successfully, but these errors were encountered: