OK. Now I know what is happening. The page I'm trying to get is a form
that uses post method to modify itself. If it detects POST it will
redirect to itself with different GET parameters, and so on. cURL is
posting even on redirect which makes this form think it has been
submitted again, and it again issues a redirect, so we end up in a
redirect loop.

I thinks this behaviour of cURL should be changes since no browser that
I know of will use POST to get page that it was redirected to. It should
use GET instead (when following a redirect).

--
Edin Kadribasic
UNIX Developer
Proventum.NET 
-----Original Message-----
From: Daniel Stenberg [mailto:daniel_at_haxx.se]
Sent: Thursday, March 22, 2001 8:05 PM
To: curl and php list
Subject: RE: HTTP post with PHP & CURL using basic
authenticationandfollowingredirect
On Thu, 22 Mar 2001, Edin Kadribasic wrote:
> I get the following output:
Is that a redirect-loop?
If that's so, the command line client sets the CURLOPT_MAXREDIRS to 50
unless
anything else is set (set a lower value with --max-redirs).
libcurl sets no default limit and unless the PHP/CURL glue layer does
this,
the PHP curl module won't have any maximum redirect limit and will
continue
forever!
-- 
  Daniel Stenberg -- curl project maintainer -- http://curl.haxx.se/
_______________________________________________
Curl-and-php mailing list
Curl-and-php_at_lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/curl-and-php
_______________________________________________
Curl-and-php mailing list
Curl-and-php_at_lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/curl-and-php