How do I redirect requests coming to http://blog.mysite.com to http://mysite.com/blog?
Reading the apache docs on when not to use the rewrite mod, I tried a simple redirect e.g.
Redirect http://blog.mysite.com http://mysite.com/blog
But when I visit http://blog.mysite.com, it doesn't redirect me. Any suggestions?
I currently have my wordpress blog (apache2, ubuntu linux) hosted at e.g. mysite.com using ID-based linking, e.g. http://mysite.com/?p=547. I have two goals:
mysite.com/blog/{post-title} instead of /?p={post-id}Moving to the new structure should be simple enough, as is changing the setting in wordpress to use the new permalink structure.
What I would also like to do is not break the random(1..100) sites that currently link to me. I would like to use an HTTP 301 permanent redirect, but I'm not sure how to do that by changing apache's settings.
The first issue will be to handle the redirection to /blog/ for all requests.
The second issue will be to handle the new link structure. I figure I can query the mysql database easily enough and generate something like ?p={post-id} > {post-title}, but I'm not sure what the syntax should look like and where I need to put it.
Any help would be much appreciated.
I want to host two different sites on the same IP, same server, and same domain using Apache2 on Ubuntu Linux. Let's say I have the following directories which represent sites that will serve content:
/srv/www/blog/ #for the blog
/srv/www/mainsite/ #for the main site
I want to set up Apache2 so that the following applies:
http://mysite.com/ they are served content from /srv/www/mainsite/.http://mysite.com/blog, they are served content from /srv/www/blog/.I had thought I was going to be setting up multiple virtual hosts, but only seems to apply for distinct domains and/or IPs. What do I need to do in my apache2 configuration to achieve the above functionality?
I have a local copy of a SQL Server DB stored as an MDF file. Is there a way to tell what version of SQL Server was used to create that file?
I need to search our mail logs for a specific e-mail address. We keep a current file named maillog as well as a week's worth of .bz2 files in the same folder. Currently, I'm running the following commands to search for the file:
grep [email protected] maillog
bzgrep [email protected] *.bz2
Is there a way combine the grep and bzgrep commands into a single output? That way, I could pipe the combined results to a single e-mail or a single file.
UPDATE:
While we were working on this problem, we realized that HTTPS traffic does not suffer from the "long url" problem (unless, of course, you have an exceptionally long domain name). This is because the query string of the URL is encrypted in an HTTPS request message and thus wouldn't be visible to a proxy or firewall. While we did adjust the maximum url length setting on our Cisco firewall (which helped), we also realized that our production site will be entirely behind HTTPS, so we won't have to worry about it anymore.
A few months ago, I was having trouble logging in to meta.stackoverflow.com and I e-mailed the Stack Overflow team for help. They pointed me to "I Can't Log In With My OpenID - Troubleshooting Tips" and that led me to believe that I may be behind an aggressive firewall or proxy that blocks long URLs. I also had trouble with other sites that used long URLs.
I'm doing testing with a 3rd party vendor's web site and their site requests .axd resources with very long query parameters. I've had lots of trouble with the functionality of their site inside our network, so I'm again thinking that a proxy or firewall is interfering.
I'm going to ask our SysAdmin team to look into this "long URL" issue, but I'd like to give them more direction about where to look, if possible. One of our SysAdmins said that he thinks we're behind a Cisco Web Application firewall. Is there a particular setting on this device that we could look at to see if it's blocking long URLs? Are there other common network components to look at to see if they are blocking long URLs?
NOTE: Here are the steps I took to determine that I think the problem is in a network component and not on my personal machine.
The 3rd party vendor's website did not work correctly when I visited their site from:
The 3rd party vendor's website worked correctly when I visited their site from:
Because the lowest common denominator when the site did not work correctly is our corporate network stack, I think the problem likely exists there.
How do I need to format a text file so that it can be read by an SMTP service to send an e-mail that has an attachment?
We have a server where we are using II6 SMTP to send mail from a Pickup folder. The goal is to drop a properly formatted text file into Mailroot\Pickup and then the file will be automatically processed and sent to the correct SMTP recipient.
For simple files, this works correctly. Here's an example of a simple file that works (domain names changed):
From:[email protected] To:[email protected] Subject:Hello World! Test Body Of The E-mail
When I drop a text file containing the above contents into the Mailroot\Pickup folder, it sends correctly. However, I haven't been able to figure out how to get an attachment to work.
I found some material that explained how to encode an SMTP attachment and another tool for simple base64 encoding conversion. Using the information on those pages, I came up with the following text:
From:[email protected] To:[email protected] Subject:Hello World! MIME-Version: 1.0 Content-Type: text/plain; boundary="Attached" Content-Disposition: inline; --Attached Content-Transfer-Encoding: base64 Content-Type: text/plain; name="attachment.txt" Content-Disposition: attachment; filenamename="attachment.txt" VGhpcyBpcyBhIHRlc3Qgb2Ygc29tZXRoaW5nIHRvIGVuY29kZS4NCk5ldyBsaW5lDQpOZXcgTGlu ZQ0KIkhlbGxvdyIgISEhDQo9PT09ICcgZnNkZnNkZiAxMjM1NDU2MzQzNA== --Attached--
However, when I place the above text in a file and drop it into Mailroot\Pickup, it doesn't send an attachment correctly. Instead, an e-mail shows up with the following in the body of the e-mail:
MIME-Version: 1.0
Content-Type: text/plain;
boundary="Attached"
Content-Disposition: inline;
--Attached
Content-Transfer-Encoding: base64
Content-Type: text/plain;
name="attachment.txt"
Content-Disposition: attachment;
filenamename="attachment.txt"
VGhpcyBpcyBhIHRlc3Qgb2Ygc29tZXRoaW5nIHRvIGVuY29kZS4NCk5ldyBsaW5lDQpOZXcgTGlu
ZQ0KIkhlbGxvdyIgISEhDQo9PT09ICcgZnNkZnNkZiAxMjM1NDU2MzQzNA==
--Attached--
I can't figure out what I need to do to format the text file so that the SMTP service correctly sends attachments.
I'm trying to install Windows Server 2008 Small Business Edition using the following hardware:
I booted to the DVD and went through the Windows installation product, entering my product key, choosing a partition, and all that stuff. Everything seemed to go smoothly until the first reboot.
When I rebooted the first time, it came back to the exact same installation screen as if the first installation attempt didn't even happen. I checked the files on the hard drive, and I can see several GB of standard Windows folders, indicating that something was copied over during the first installation attempt.
If I remove the Windows DVD from the drive and reboot, I'm brought to a screen that simply says:
NO BOOTABLE PARTITION FOUND IN TABLE
What might I try to do to resolve this problem?
If I have the following records in the DNS:
hostname Record Type address
benmccormack.com A 216.10.244.61
www.benmccormack.com CNAME benmccormack.com
What should the user expect to see in a browser's address bar when they type in http://benmccormack.com? how about http://www.benmccormack.com? I was expecting that I would see http://www.benmccormack.com change to http://benmccormack.com in the address bar, but perhaps I misunderstand how a CNAME record is supposed to work.
(Note: I just updated the dns for my site about 15 minutes ago, so perhaps the changes haven't propagated yet.)