Unused?: the url tag in the DPI start_send_page command

[Jeremy Henty]

Everything that sends the start_send_page DPI command also sends a url
attribute with it, but I think this attribute is always ignored.

Dillo processes the command in capi.c but it does nothing with it
because the Cache is already set up to receive the following raw data.
So it doesn't look at any attributes. The only other thing that
receives a start_send_page is the view source DPI and it doesn't look
at any of the attributes either (it extracts a url from the previous
tag in the stream, which it then sends back to Dillo to be ignored).

So what is this attribute for? Future use? Or is it something that
just never got used?

Regards,

Jeremy Henty

[Jorge Arellano Cid]

Post by Jeremy Henty
Everything that sends the start_send_page DPI command also sends a url
attribute with it, but I think this attribute is always ignored.
Dillo processes the command in capi.c but it does nothing with it
because the Cache is already set up to receive the following raw data.
So it doesn't look at any attributes. The only other thing that
receives a start_send_page is the view source DPI and it doesn't look
at any of the attributes either (it extracts a url from the previous
tag in the stream, which it then sends back to Dillo to be ignored).

View source shows the URL as page title.

Post by Jeremy Henty
So what is this attribute for? Future use? Or is it something that
just never got used?

In general terms, there were ideas that went unused, and some
extensions that were necessary to solve an unforeseen situation;
as dpi authentication to avoid a local socket spoofing attack.

The dpi framework is the same for several quite different dpi
programs (aka plugins). The interface was kept more or less
uniform, and each dpi chooses whether to use the info or not.

[Jeremy Henty]

Post by Jorge Arellano Cid

Post by Jeremy Henty
Everything that sends the start_send_page DPI command also sends a
url attribute with it, but I think this attribute is always
ignored.
Dillo processes the command in capi.c but it does nothing with it
because the Cache is already set up to receive the following raw
data. So it doesn't look at any attributes. The only other thing
that receives a start_send_page is the view source DPI and it
doesn't look at any of the attributes either (it extracts a url
from the previous tag in the stream, which it then sends back to
Dillo to be ignored).

View source shows the URL as page title.

Yes, but it gets that url from the open_url tag that Dillo sends
first. The DPI then reads the start_send_page tag but ignores its url
attribute. Nothing reads the url attribute from any start_send_page
tag.

Regards,

Jeremy Henty