REQUEST A DEMO

Tag: iis

SDK based web apps in a 64-bit environment

June 17, 2011 I wanted to drop a little update regarding some upcoming changes, specifically in regards to our classic web applications (Dovetail Agent, Dovetail Admin, and Dovetail SelfService) operating in a 64-bit environment.   If you’re not running one of those web apps in a 64-bit environment, then don’t sweat this post – head off and read something more interesting :) Currently, we require our classic web apps to run in a 32-bit mode. Why? Because the Dovetail SDK is currently 32-bit only but that will change with SDK version 3.0.   Update: 3/28/2012:   Now that Dovetail SDK 3.0 has been released (which supports both 32 and 64-bit COM objects), I wanted to drop a little update here.   Dovetail Agent 4.5 can now be run in 64-bit mode. This requires the 64-bit version of SDK (version 3.0 or higher) be installed.   Dovetail Admin (any version) can…

Everyone play nice: BOLT, OLEDB, Oracle, 64-bit Windows

May 27, 2011 With 64-bit machines becoming more and more prevalent, we’ve seen some confusion popup around installing and using applications. Is the app 32-bit? 64-bit? which database provider do I use? Is my web app 32 or 64 bit? etc. It’s confusing. No doubt. tl; dr Short answer:  If you’re on a 64-bit machine, and using Oracle, use the 64-bit Oracle provider for OLE DB for BOLT. 64-bit Windows explained There’s a great post from last year that “explains 64 bit”: Programs are still in the same place, in %ProgramFiles%, unless you need the 32 bit version, which is in %ProgramFiles(x86)%, except on a 32 bit machine, where it’s still %ProgramFiles%. All those dll’s are still in %SystemRoot%System32, just now they’re 64 bit. The 32 bit ones, they’re in %SystemRoot%SysWOW64. You’re with me so far, right? Oh, and the 16 bit ones…

Using the URL Rewrite module to set your cookies to HttpOnly

January 20, 2011 A question recently arose about how to set a cookie to be HttpOnly. An HttpOnly cookie is one that cannot be accessed through client-side script. Any information contained in an HTTP-only cookie is less likely to be disclosed to a hacker or a malicious Web site. The use of HTTP-only cookies is one of several techniques that, when used together, can mitigate the risk of cross-site scripting. Setting a cookie to be HttpOnly One way to set a cookie to be HttpOnly is to change how you define it. Rather than something like this: Response.Cookies("mycookie") = “foo”; We can do this: Response.AddHeader "Set-Cookie", "mycookie=foo; HttpOnly" Pretty simple. What about cookies you don’t create yourself? This works great for cookies that you create yourself. But what about those that are created by IIS and ASP, such as the ASPSESSION cookie? One…

IIS Configuration and Permissions for remote file attachments

September 1, 2010 While setting up some advanced capabilities of DovetailAgent, we ran into some IIS/Windows permission issues. This post is to capture and share some of the learnings.   To start with, Kevin Miller has a good post on installing Classic ASP web application on IIS7.   The “advanced” capabilities I’m referring to was setting up file attachment uploads, and saving those files off to a permanent file storage area, accessed by a UNC drive such as \\fileServer\attachments   Environment: Windows Server 2008, Dovetail Agent 4.3 File Uploads   The way file uploads work is that the file is first uploaded to the web server where DovetailAgent is running. Then, the application moves the file to the permanent storage location, which is commonly a share on a different server. The application also creates directories and subdirectories where needed. So if your base attachment directory is\\fileServer\attachments,…