[GH-ISSUE #22] Provide a way to create signed URL requests without OAuthSwiftHTTPRequest #14

New issue

Closed

opened 2026-03-03 16:44:48 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 16:44:48 +03:00

Owner

Originally created by @bizz84 on GitHub (Jan 27, 2015).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/22

The OAuthSwiftClient class does a good job at creating Authorization Headers for the client URL requests, however it seems that the only way to actually send the requests is by using this class directly.

It would be nicer to have a URL request builder based on OAuthSwiftClient that can be used to generate requests, while letting the client decide how to send them (e.g. Alamofire).

I have already built a sample implementation for this:
https://github.com/bizz84/OAuthRequestBuilderSwift

Would be nice to see this integrated into OAuthSwiftClient.

Originally created by @bizz84 on GitHub (Jan 27, 2015). Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/22 The OAuthSwiftClient class does a good job at creating Authorization Headers for the client URL requests, however it seems that the only way to actually send the requests is by using this class directly. It would be nicer to have a URL request builder based on OAuthSwiftClient that can be used to generate requests, while letting the client decide how to send them (e.g. Alamofire). I have already built a sample implementation for this: https://github.com/bizz84/OAuthRequestBuilderSwift Would be nice to see this integrated into OAuthSwiftClient.