Accessing a collection from outside of Apex without causing a HTTP redirect

Question

First, some background:
I am running Apex version 2.2.1.00.04 on Oracle9i Enterprise Edition Release 9.2.0.7. IE 6 and Flash 9
My Apex page contains two third-party Flash controls. Each Flash control uses a passed in URL to get the data that it will display. The data that I need to pass to the Flash controls is stored in an Apex collection created in my page.
Using the technique outlined in the following posts,
Re: Accessing Collection through a DBMS.job
Re: Accessing application item value from database
I have created a stored procedure that will attach to my Apex session and query the collection. See procedure get_data below.
The URL that the Flash controls are passed is like this:
http://myhost/pls/mydad/get_data?p_user=MYUSER&p_session_id=535622580488397200&p_app_id=2332
The call to WWV_FLOW_CUSTOM_AUTH_STD.POST_LOGIN causes a HTTP redirect to the Apex at page p_app_id:1. The Flash control that initiated the request never sees the data stream that the get_data procedure is sending via HTTP.P. Instead, it sees the HTML produced by the Apex page at p_app_id:1.
Now, my question:
Is it possible to call the WWV_FLOW_CUSTOM_AUTH_STD.POST_LOGIN command in away that does not cause a HTTP redirect? If not, then is there another series of commands that will attach to an Apex session but not cause a HTTP redirect?
Thanks,
Ken
CREATE OR REPLACE procedure get_data(p_user IN VARCHAR2,
p_session_id IN VARCHAR2,
p_app_id IN VARCHAR2) as
BEGIN
APEX_CUSTOM_AUTH.DEFINE_USER_SESSION(p_user,
p_session_id );
APEX_APPLICATION.G_FLOW_ID:= p_app_id;
WWV_FLOW_CUSTOM_AUTH_STD.POST_LOGIN(p_user ,
NULL ,
p_session_id ,
p_app_id||':'||'1' );
FOR c_collection_rec IN (SELECT c001
FROM APEX_COLLECTIONS
WHERE collection_name='MY_COLLECTION')
LOOP
HTP.P(c_collection_rec.c001);
END LOOP;
END;

Answer 1

Ken - No way to prevent the redirect attempt, that's what the procedure is built to do. To use it otherwise is aberrant. I think you could use an on-demand process (FOO) callable from the URL that would spit the data back out. You do this by defining an application process (on-demand firing point) and callling it from the URL ( f?p=APP:0:SESSSION:APPLICATION_PROCESS=FOO). If the cookie is passed in the request (meaning you've authenticated) and authentication check passes again in your process request, the process will produce the result stream.
Scott