httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darryle Steplight <dstepli...@gmail.com>
Subject Re: [users@httpd] Question about how to fetch html?
Date Fri, 12 Jun 2009 22:06:02 GMT
I suggest using a server side language like PHP to do the heavy
lifting for you. There are pre-existing functions out there that
already take care of this.

On Fri, Jun 12, 2009 at 5:47 PM, Brian Kim<09su.research@gmail.com> wrote:
> Thanks.
>
> Sorry for unclear explanations.
>
> Basically I want to make my proxy system do (1) parsing the html data,
> (2) analyzing the html data, (3) modifying some of the html data and
> then sending it to users.
>
> Here, the problem is that it is hard to finish (1), (2) & (3) jobs
> before sending the html data.
>
> I am looking for the way of implementing it.
>
> Does André or anybody have any idea?
>
>
>
> On Fri, Jun 12, 2009 at 5:15 PM, André Warnier<aw@ice-sa.com> wrote:
>> Brian Kim wrote:
>>>
>>> Hi all.
>>>
>> Hi Brian.
>>
>>> Currently I am creating a http-based proxy system to fetch a html data
>>> between users' browser ans web server.
>>
>> That's usually what browsers do already, but ok..
>>
>>>
>>> In fact, I did it by adding some code in
>>> ap_proxy_http_process_response function as follows
>>>
>> ... some courageous lines removed for clarity here ...
>>
>>>
>>> By the way, this given code seems to repeat getting a partial html and
>>> passing it down.
>>
>> Yep, that's usually what webservers do. And proxies too.
>> Suggestions and patches for improvement are always welcome though.
>>
>> However, I want to parse the complete html, analyze it and send it to users'
>> browser.
>>
>> Well, the browser already does that all by itself, so it's not clear what
>> your purpose is, here.
>>
>>>
>>> By concatenating the partial html, I can create a complete html data
>>> and parse it.
>>
>> That basic idea is ok.
>>
>> However, it only can happen after the html is already sent according to the
>> above program structure.
>>
>> Don't understand exactly what structure you're referring to, but yes, it is
>> hard to parse the html before the server sent it.
>>
>>>
>>> Does anyone know about how to fix this problem?
>>
>> It is not quite clear what the problem is, here.
>>
>> Is there any general way to fetch html?
>>>
>>
>> With a browser maybe ?
>>
>> ;-)
>>
>>
>> ---------------------------------------------------------------------
>> The official User-To-User support forum of the Apache HTTP Server Project.
>> See <URL:http://httpd.apache.org/userslist.html> for more info.
>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>  "   from the digest: users-digest-unsubscribe@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>   "   from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>



-- 
A: It reverses the normal flow of conversation.
Q: What's wrong with top-posting?
A: Top-posting.
Q: What's the biggest scourge on plain text email discussions?

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message