Activity log for bug #806713

Date Who What changed Old value New value Message
2011-07-06 22:40:48 Martin Pool bug added bug
2011-07-22 03:59:01 Martin Pool tags loggerhead loggerhead privacy private
2011-07-22 04:01:07 Martin Pool description https://code.launchpad.net/~spiv/launchpad/bmp-inline-diffs/+merge/66634 and friends take the approach of proxying client requests through the main app domain to loggerhead. This probably isn't going to work for private branches, because (iiuc) loggerhead uses a separate authentication cookie, so the client is going to send the cookie relevant to say code.l.n and loggerhead won't know what to do with it. One solution would be to teach loggerhead to validate the cookie by calling across to lp. https://code.launchpad.net/~spiv/launchpad/bmp-inline-diffs/+merge/66634 and bug 816349 and friends take the approach of proxying client requests through the main app domain to loggerhead. This probably isn't going to work for private branches, because (iiuc) loggerhead uses a separate authentication cookie, so the client is going to send the cookie relevant to say code.l.n and loggerhead won't know what to do with it. One solution would be to teach loggerhead to validate the cookie by calling across to lp.
2011-07-22 04:01:54 Martin Pool description https://code.launchpad.net/~spiv/launchpad/bmp-inline-diffs/+merge/66634 and bug 816349 and friends take the approach of proxying client requests through the main app domain to loggerhead. This probably isn't going to work for private branches, because (iiuc) loggerhead uses a separate authentication cookie, so the client is going to send the cookie relevant to say code.l.n and loggerhead won't know what to do with it. One solution would be to teach loggerhead to validate the cookie by calling across to lp. https://code.launchpad.net/~spiv/launchpad/bmp-inline-diffs/+merge/66634 and bug 813349 and friends take the approach of proxying client requests through the main app domain to loggerhead. This probably isn't going to work for private branches, because (iiuc) loggerhead uses a separate authentication cookie, so the client is going to send the cookie relevant to say code.l.n and loggerhead won't know what to do with it. One solution would be to teach loggerhead to validate the cookie by calling across to lp.
2011-11-24 16:15:42 Curtis Hovey tags loggerhead privacy private loggerhead privacy
2013-12-03 09:15:43 William Grant marked as duplicate 904070