Be the first to post a text review of Yoctoprox(y). Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Code committed

  aaronthemad committed revision 4 to the Yoctoprox(y) SVN repository, changing 1 files

  posted by aaronthemad 355 days ago

• Code committed

  aaronthemad committed revision 3 to the Yoctoprox(y) SVN repository, changing 1 files

  posted by aaronthemad 355 days ago

• Code committed

  aaronthemad committed revision 2 to the Yoctoprox(y) SVN repository, changing 1 files

  posted by aaronthemad 355 days ago

• Code committed

  aaronthemad committed revision 1 to the Yoctoprox(y) SVN repository, changing 1 files

  posted by aaronthemad 355 days ago

• Tracker artifact added

  Anonymous created the Problem to download the PHP Script artifact

  posted by nobody 1161 days ago

• 0.4.4a - Better CSS support

  Yoctoprox now locates and translates CSS links using the @import and url() syntax. This means that standards-stringent sites like Wikipedia will now display properly. (On the downside, it will translate all instances of @import and url(), even if they're showing up in the readable text of the site. So if you're reading a site about CSS that gives examples of this notation, those examples may get translated by Yoctoprox when they really shouldn't.)

  posted by aaronthemad 1363 days ago

• File released: /yoctoprox/Yoctoprox(y) 0.4.4a/yoctoprox-0.4.4.php

  posted 1363 days ago

• yoctoprox Yoctoprox(y) 0.4.4a file released: yoctoprox-0.4.4.php

  posted 1363 days ago

• File released: /yoctoprox/Yoctoprox(y) 0.4.3a/yoctoprox-0.4.3.php

  posted 1369 days ago

• (0.4.3a) Now supports HTTP auth

  This isn't a big update in terms of the number of lines of code, but it implements one of my big functionality targets. Yoctoprox can now handle HTTP authentication. That's authentication that's initiated by a "WWW-Authenticate" header from a web server. In most web browsers, it causes a little grey window to pop up that asks you for a username and password, which the browser then caches and sends back with every file request to that server (for that auth domain, anyway). My implementation of this in Yoctoprox is very simple. Yoctoprox just detects the header, and passes it on to the user's browser. Then the browser handles the domain-matching and the caching and all as per usual. The upside to this is that it is a very concise solution, and it makes Yoctoprox as flexible as the end user's browser, in terms of auth schemes (in case they ever come up with something other than Basic and Digest). The downside is that it leaves authentication browser-based, when it's possible that Yoctoprox could handle the authentication on its own, thus providing access to digest-authenticated websites, for users of browsers which don't do digest authentication yet (if there are any of those still). On the other hand, I could think of no simple and secure way of Yoctoprox doing the necessary password cacheing. It would either require a database or reliance on the PHP sessions interface (which may or may not be secure, depending on the individual system's setup). There are also the usual downsides to browser-based password cacheing. If you want to log out of a site where the browser has cached the password, you can only do so by restarting the browser. Yoctoprox could definitely provide the means to log out more easily, by no longer forwarding on the username and password. But this setup should work for now. I think next I'll tackle cookies.

  posted by aaronthemad 1369 days ago