Member Avatar for Mahen

Opera is the only browser that supports a site by site Management compared to other browsers. In Opera, if you click on Tools > Preferences > Advanced > Cookies > Manage Cookies, you will get access the “Server Manager” window showing you a list of all the websites that you browsed with Opera since it’s first install.

This Module does not only allow you to manage the way Opera accepts Cookies, but mush more than that. If you click on a website and than on the Edit button, the Site preference window will show up. This window contains multiple tabs so as to furthur customize the way Opera is going to load these pages.

The “General” Tab is where you can customize weather Opera should allow the page to show “Popups”. The “Cookies” Tab gives you a more advanced view of the cookies that the website has transacted with you. This page asks you either to allow cookies , allow only form that website or not to accept anything. Below, you can get a listbox of all the cookies that that specific site has shared with you. If you double-click on one of them, the “Cookie Information” window appears and gives you all the information about that cookie, such as expiry date, the value that it stores, and so on.

The “Content” tab allows you to weather allow GIF/SVG animation, to enable sound in webpages, to allow Java or Plugins. The “Display” Tab allows you to customize the way Opera will display the frames of that particular website. The “Scripting” tab, as it’s name suggests, allows you to configure Opera the way it is going to process javascripts.

Finally, we have the “Network”, where we can customize “Automatic Redirection”, “Referrer logging” or “International Web Addresses in UTF 8”. However, the most powerful option is the “Browser Identification” where we can configure how Opera will Identify itself in it’s User agent String.

  • 2 Contributors
  • 1 Reply
  • 287 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by MattEvans

Dani AI

Generated

Good summary from — a couple of clarifications and practical tips that add value to the thread, plus a short reply to .

Changing the Browser Identification is useful, but it only alters the User‑Agent string the server sees; it does not make Opera behave like another browser (it does not add other engines, ActiveX support, or different JavaScript/CSS implementations). That means UA switching can coax poorly written server sniffers into serving alternate markup, but it won’t magically fix engine-level incompatibilities. (scss.com.au)

A short troubleshooting workflow to keep in your toolkit:

  1. Try a temporary Identify‑as change for the single site and reload to see whether the server serves different HTML/CSS.
  2. If the page still misbehaves, clear the cookies for that domain and remove the site entry from Opera’s Server Manager (this removes any per‑site rules that might be causing the problem), then reload.
  3. If a specific rule is needed (scripts, cookies, plugins), reapply it only for that domain and document what you changed so you can revisit it later. Steps to view and remove site cookies/entries are covered in Opera cookie/Server Manager guidance. (sra.tal.net)

Practical cautions and best practices: use UA spoofing only as a temporary workaround (it can affect analytics and cause other sites to behave unexpectedly), prefer developer tools and progressive debugging to understand the real incompatibility, and adopt a “deny by default, allow per‑site” approach for scripts/plugins — it’s safer and makes per‑site rules easier to reason about.

Member Avatar for MattEvans

However, the most powerful option is the “Browser Identification” where we can configure how Opera will Identify itself in it’s User agent String.

Unless Opera then automatically emulates the browser it identifies itself as, that's hardly a good feature! Alot of developers use that string to serve alternative content based on the type of browser they think is requesting a page; which is always gonna be for the enduser's benefit.

Still, it's gotta be worth checking out, maybe it renders HTML/CSS more intuitively than IE and FF :mad:

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.