Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of cgsmcmlxxv@gmail.com
 designates 209.85.161.52 as permitted sender)
Message-ID: <4E84D996.3080802@gmail.com>
Date: Thu, 29 Sep 2011 22:48:22 +0200
From: CGS <cgsmcmlxxv@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: CouchDB cookie from outside CouchDB
References: <4E8189D3.7080905@gmail.com>
	<CAD2UGCV8V=x8dY1OY-BaCXOY5tAiH-MM3rCiz0zUkLO=uGoF0w@mail.gmail.com>
	<4E84A003.4030300@gmail.com>
	<CAJNb-9rhkXgrGMSY0gepjgFuZCz8o16zxLRcQ_+PTeg7oxBD-A@mail.gmail.com>
 <CAD2UGCXSQ_iYPrMzFFXTnfAVFxEx6V37KMnz5MnvKCxBLQOnRA@mail.gmail.com>
In-Reply-To: 
 <CAD2UGCXSQ_iYPrMzFFXTnfAVFxEx6V37KMnz5MnvKCxBLQOnRA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks, Dale. I will follow this suggestion (also Benoit suggested the 
same). I admit I didn't think of that before and both inputs are most 
appreciated.

Port 80 is handled by YAWS (required by the other applications because 
it's Erlang). In this moment I just need to update my YAWS version (I hope).

Thanks again to both of you for your support.

Cheers,
CGS


On 09/29/2011 10:11 PM, Dale Harvey wrote:
> how are you binding to port 80? if you have nginx / apache then you can have
> a reverse proxy, couch also has an in build reverse proxy built in, I would
> suggest going down that route before dealing with cross domain issues, there
> are a lot of them
>
> On 29 September 2011 17:45, Benoit Chesneau<bchesneau@gmail.com>  wrote:
>
>> On Thu, Sep 29, 2011 at 6:42 PM, CGS<cgsmcmlxxv@gmail.com>  wrote:
>>> First of all, thank you Dale for your answer. Still, the problem is more
>>> complex than I anticipated.
>>>
>>> I am using YAWS as web server and it doesn't support proxy, so, I have to
>>> use two different ports for the two (CouchDB and YAWS). Methods I have
>>> tried:
>>> 1. $.ajax() - error: not allowed cross-domain data transfer via
>> JavaScript
>>> (both IP and port should match exactly for both origin and target), so,
>> even
>>> if correct authentication, no cookie.
>>> 2. form action pointing to
>>> server_name:5984/_session?next=/path_to_attachment/back.html - error: if
>> the
>>> authentication fails (incorrect username/password), the "next" is no
>> longer
>>> taken (back.html contains only window.location which redirects back to
>>> YAWS), but it goes back if the authentication doesn't fail.
>>>
>>> I would appreciate any idea related to how to solve any of these errors.
>>> Thank you.
>>>
>>> Cheers,
>>> CGS
>>>
>>>
>> can't you use the reverse proxy module of yaws ? Othere way would be
>> having an iframe. Waiting CORS (patch should be available on friday,
>> was busy).
>>
>> - benoit
>>