Date: 11/14/99
- Next message: Padraic Renaghan: "Re: [PHPLIB-DEV] cvs commit (cache-control)"
- Previous message: Padraic Renaghan: "Re: [PHPLIB-DEV] cvs commit"
- In reply to: Padraic Renaghan: "Re: [PHPLIB-DEV] cvs commit"
- Next in thread: Padraic Renaghan: "Re: [PHPLIB-DEV] cvs commit (cache-control)"
- Reply: Padraic Renaghan: "Re: [PHPLIB-DEV] cvs commit (cache-control)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
(Sorry if I skip the largest part of your email, but I
currently don't have the time to dig into it.)
> If PHP gets fixed, then putting the source code back to sending two
> cache-control lines sounds right to me.
Following RFC 2616, 4.2 Message Headers, multiple
message-headers with the same field-name are legal, if the
field-value is defined as a comma-separated list.
That is true for cache-control and numerous other header
fields.
The PHP group is currently looking into possibilities to make
PHP behave correctly.
--Regards,
Sascha Schumann Consultant - PHPLIB Developers Mailing List. Send messages to <phplib-dev <email protected>>. To unsubscribe, send "unsubscribe" to <phplib-dev-request <email protected>> in the body, not the subject, of your message.
- Next message: Padraic Renaghan: "Re: [PHPLIB-DEV] cvs commit (cache-control)"
- Previous message: Padraic Renaghan: "Re: [PHPLIB-DEV] cvs commit"
- In reply to: Padraic Renaghan: "Re: [PHPLIB-DEV] cvs commit"
- Next in thread: Padraic Renaghan: "Re: [PHPLIB-DEV] cvs commit (cache-control)"
- Reply: Padraic Renaghan: "Re: [PHPLIB-DEV] cvs commit (cache-control)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

