![]() Packages (timestamps in pop-ups are UTC):ĭependencies NOTE: FreshPorts displays only information on required and default dependencies. PKGNAME: elinks Flavors: there is no flavor information for this port. NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. To install the port: cd /usr/ports/www/elinks/ & make install clean To add the package, run one of these commands: share/locale/pt_BR/LC_MESSAGES/elinks.mo./usr/local/share/licenses/elinks-0.15.1/GPLv2./usr/local/share/licenses/elinks-0.15.1/LICENSE./usr/local/share/licenses/elinks-0.15.1/catalog.mk.Syntax highlighting for HTML, RSS, and XBEL – – – – pkg-plist: as obtained via: make generate-plist Expand this list (42 items) Collapse this list. Support for editing textareas in external editorĪbility to switch off document-specific colors Some very minor features not worth mentioning hereĬookie expiration and saving/loading from disk New translations and some updates of the original ones ![]() NOTE: the Look for it right after the Description: on each port's home page.Įlinks Links text So far elinks adds the following to links: Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15) HTTP, Archeology and Web Compatibility issues that seems to be close enough from my vices.FreshPorts - www/elinks: Links text WWW browser with enhancementsĪs an Amazon Associate I earn from qualifying purchases. If I was silly enough, maybe I would do this. Maybe it would be worth to document indeed how it is working as implemented now and how it is supposed to be working when there's no interoperability. Should it be documented? Well, there are plenty of issues, there are plenty of hacks around it. Refresh is no longer in the HTTP/1.1 document - it has been deferred to To individual objects (RE: the message below to netscape). My concern with "Refresh" is that I do not want it to be a globalĬoncept (a browser can only keep track of one refresh)-it looks to be In June 1996, Jerry Jongerius posted about HTTP/1.1 Refresh header field comments So another thing you obviously want to do, in addition to causing the currentĭocument to reload, is to cause another document to be reloaded in n seconds (Thanks to SecuriTeam Web site and Amit Klein) The earliest mention seems to be An Exploration Of Dynamic Documents I can't find anywhere the documentation for Refresh HTTP header on old Netscape Web sites. I can find very early references of meta refresh such as in Netscape Developer documentation. My guess is the 301 always win with the Location HTTP header, or at least it's what I hope. HTTP / 1.1 301 Permanent Redirect Refresh : 0 url= Location : Then what about scripts, stylesheets, JSON files, HTML document in iframes, etc? For the SetupRefreshURIFromHeader code, there are Web Compatibility hacks in the source code of Firefox. For now, the refresh is not done for inline resources. The bug is what the browser should do when the Refresh HTTP header is on an image included in a Web page (this could be another test). This bug about inline resources is quite interesting and might indeed need to be addressed if there was a documentation. On Mozilla bug tracker, there are a certain number of bugs around refresh. If someone could test for IE and Chrome at least. Yes - Chrome (something) said Hallvord ).HTTP / 1.1 200 OK Accept-Ranges : bytes Connection : Keep-Alive Content-Length : 200 Content-Type : text/html charset=utf-8 Date : Thu, 05:48:57 GMT ETag : "c8-5122a67ec0240" Expires : Thu, 05:48:57 GMT Keep-Alive : timeout=5, max=100 Last-Modified : Thu, 05:37:05 GMT Refresh : 0 url=
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |