At 12:42 PM +0200 8/20/07, Wouter van Vliet / Interpotential wrote:
Only thing I was trying to do was chip in my two cents. Again, I
wasn't the one who originally asked the question and I certainly am
not "friggen clueless".
Maybe not, but you made some pretty clueless remarks -- like if you
On 20/08/07, tedd <[EMAIL PROTECTED]> wrote:
>
> At 10:40 PM +0200 8/19/07, Wouter van Vliet / Interpotential wrote:
> >What you're proposing, is to actually display some content on another
> page
> >then were the content is originally intended? I'm sorry, but I would
> >consider that 'bad practice
At 10:40 PM +0200 8/19/07, Wouter van Vliet / Interpotential wrote:
What you're proposing, is to actually display some content on another page
then were the content is originally intended? I'm sorry, but I would
consider that 'bad practice'. To me, it makes perfect sense that you don't
want to le
What you're proposing, is to actually display some content on another page
then were the content is originally intended? I'm sorry, but I would
consider that 'bad practice'. To me, it makes perfect sense that you don't
want to leave the user on the page where login was originally handled. For
vario
At 8:52 AM +0200 8/19/07, Otto Wyss wrote:
In my case I could easilly do without redirection but just exit and
fall back on the calling page. Yet I want to remove the login page
from the browser history. Does the header function have the same
effect?
O. Wyss:
Instead of messing with the us
On Sat, 18 Aug 2007 17:03:35 +0200, "M. Sokolewicz" wrote:
> The reason why setting cookies for you doesn't work is because of the
> way a HTTP response is structured. It consists of 2 parts: header and
> body separated by 2 new lines (\n\n). It is _required_ that _all_
> headers come _before_
M. Sokolewicz wrote:
emits). Now, I'm not going to go into how redirecting that way won't
work (or at least shouldn't), but a hint would be to do it properly
using header('Location: [...]') instead.
I'm aware that using Javascript within a PHP code block doesn't seems
logical yet I haven't know
M. Sokolewicz wrote:
On a sidenote, 99% of the world never calls ob_flush (or any such
function) since PHP flushes the buffer automatically at the end of its
execution.
I'll keep the ob_end_flush just for showing what's going on, but thanks
for the hint.
The reason why setting cookies for y
bullshit,
what he sees is a warning emitted by PHP, his redirect is done using
JavaScript (which is clientside and has no, 0.0 effect on what PHP
emits). Now, I'm not going to go into how redirecting that way won't
work (or at least shouldn't), but a hint would be to do it properly
using head
Hi,
Its not the problem of cookies. Its problem of redirection or the
parent.location.replace function. I mean if you already output something on
the page and tries to redirect then this problem happens.
Redirect before outputting anything on the page.. like space is also an
output.
Warm Regards,
up on server documentation
bastien
To: php-general@lists.php.net; [EMAIL PROTECTED]
Date: Sat, 18 Aug 2007 16:39:29 +0200
From: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]; php-general@lists.php.net
Subject: Re: [PHP] Cookies and sent headers
ob_start() at the beginning and ob_end_flu
m: [EMAIL PROTECTED]
> CC: [EMAIL PROTECTED]; php-general@lists.php.net
> Subject: Re: [PHP] Cookies and sent headers
>
> ob_start() at the beginning and ob_end_flush() at the end of the PHP
> section seems to do the trick albeit I've still problems to understand
> why. The des
ob_start() at the beginning and ob_end_flush() at the end of the PHP
section seems to do the trick albeit I've still problems to understand
why. The description in the manual is rather sparse unfortunately. Is
there any more information about what's going on?
O. Wyss
Wouter van Vliet / Interp
sessions and cookies either need to be set at the beginning of the page, or you
can look into the ob_start(), ob_flush() functions to use output buffering
bastien
> To: php-general@lists.php.net
> Date: Sat, 18 Aug 2007 11:25:54 +0200
> From: [EMAIL PRO
You best option would be to go through all of your include'd or require'd
files and make sure there is no whitespace before and after you open your
php tags. Those are often the cause for such problems. The easy way would
indeed be to use output buffering. In that case, put the call to ob_start();
Kelvin Park wrote:
Otto Wyss wrote:
If built a simple login page and store any information within
$_SESSION's. Yet I'd like to move these into cookies but I always get
an error about sent headers. Is there a way to circumvent this
problem without changing too much in the page?
The setting of
16 matches
Mail list logo
