Re: [aur-dev] Output buffering and header() usage

2011-06-22 Thread Lukas Fleischer
On Tue, Jun 21, 2011 at 11:19:29AM -0500, Dan McGee wrote: > On Tue, Jun 21, 2011 at 11:11 AM, Lukas Fleischer > wrote: > > Some possible solutions/workarounds that came into my mind: > > > > * Use javascript redirects instead. > > > > * Just buffer output everywhere (ob_start(), ob_flush()). > >

Re: [aur-dev] Output buffering and header() usage

2011-06-21 Thread elij
On Tue, Jun 21, 2011 at 9:19 AM, Dan McGee wrote: > On Tue, Jun 21, 2011 at 11:11 AM, Lukas Fleischer > wrote: >> Some possible solutions/workarounds that came into my mind: >> >> * Use javascript redirects instead. >> >> * Just buffer output everywhere (ob_start(), ob_flush()). >> >> * Rewrite p

Re: [aur-dev] Output buffering and header() usage

2011-06-21 Thread Dan McGee
On Tue, Jun 21, 2011 at 11:11 AM, Lukas Fleischer wrote: > Some possible solutions/workarounds that came into my mind: > > * Use javascript redirects instead. > > * Just buffer output everywhere (ob_start(), ob_flush()). > > * Rewrite package search to retrieve package search results before even >

[aur-dev] Output buffering and header() usage

2011-06-21 Thread Lukas Fleischer
Trying to reproduce FS#24580 [1] I stumbled upon a design flaw that apparently remained concealed for a long time due to a series of (un-)fortunate circumstances. Short summary of the bug report for reference: A package search currently seems to erroneously return an empty search result, if * Rus