Download & Extend

discovery broken, does not check headers for XRDS location if a 403 error is returned.

Project:OpenID
Version:5.x-1.x-dev
Component:OpenID Client
Category:bug report
Priority:normal
Assigned:Unassigned
Status:needs review

Issue Summary

I was having difficulty with discover, and I do not want to enable permissions to view profiles for anonymous users... I did notice that the XRDS-Location: header is set even is result->error is true. This patch modified discovery to go ahead and check the headers... It may be overkill, but gets the job done.

AttachmentSize
openid-discovery.patch4.42 KB

Comments

#1

here is a slightly cleaner patch without the debugging.

AttachmentSize
openid-discovery.patch 3.89 KB
nobody click here