Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "301"
Today we have an exciting devRant announcement! As many observant members of the community have problably noticed, since launch we've been using the domain name devrant.io since the .com was already taken. Today, we're happy to announce, we now own devrant.com and it is now the official devRant URL!
How did this happen you ask? The devrant.com domain was already owned by a developer named Wiard when we launched devRant. It took a while to track him down, but when we did, turned out he saw the good we were doing and wanted to help the devRant community by generously offering us the .com domain for a very reasonable exchange (considering that we are a self-funded bootstrapped startup!).
Since Wiard recently started writing a blog on devrant.com, he had to find a new home for it. His new blog is https://sysrant.com and I encourage everyone to check it out! Great topical/educational dev/sys-admin related articles? Check. Someone who cares about the devRant community and allowed us to leave the firey hell that is .io? Check. So check it out!!
Some technical info:
This change is immediate and all devrant.io non-api requests will now redirect to devrant.com. We might have missed a few things (purposely or accidentely) so we're going to be going through and converting anything that's left. If you use the devRant API, your implementation should not break since API requests are meant to be excluded for now, but I highly recommend switching any API URLs to https://devrant.com so you can avoid issues in the future if we decide to stop redirecting devrant.io API requests. Also one note, there was an issue for about a minute after we turned on the redirected where some API requests to devrant.io might have 301 redirected to devrant.com. If an app you were using broke, try clearing whatever cache the 301 redirect might be stored in and the issue should go away.
Feel free to post any questions you might have here (and please let me know about any issues you might discover!), and once again, huge thanks to Wiard!79
Dear nerds from all over the world,
We get it. 404 pics are funny.
But did you know there other status codes too?
204 - No Response
301 - Moved
302 - Found
400 - Bad request
401 - Unauthorized
402 - Payment Required
403 - Forbidden
501 - Not Implemented
502 - Service Temporarily Overloaded
I'm sure you'll also find funny situations with these.
Thanks. We're the best!26
I am at +301. How do I know for sure my ++ count isn't frozen and I actually have a billion ++'s??11
My boss says to me this morning.
Boss: Can you add these links as a redirect 301 to this link.
Me: Ok, I'm not the developer for that domain but I guess I can do it. Let's try to update apache htaccess for that domain through my account.
(After a swift ssh connection to the server to check out that domain.)
Me: Er...boss, we don't own that domain. We cannot redirect it's links to our other domains.
Boss: Why? What do you mean?!
Me: well if we don't own that domain, than it is not on our server and we cannot update it's server config files. So we cannot redirect that domain to our other domains.
Boss: Are you sure?
It went on like this for a while. I had a laugh break after.1
I've seen some rants about people complaining about websites using the 'www' subdomain, so I'd like to take this opportunity to try to explain my opinion about why sites might use it.
I use to feel the same way about not having the www subdomain. It felt like an outdated standard that serves no purpose. But I have changed my option...
Sometimes certain servers have other services running other than just the website, such as ssh, ftp, sql, etc., running on different ports. What if you want to use a web proxy and caching service similar to cloudflare or a cdn? We'll you can't, because they won't allow traffic to flow through to your other ports.
That's where the www subdomain comes in. Enable your caching and cdn on your www subdomain, and slap a 301 redirect from your primary domain on port 80 or 443 to the www subdomain. This still allows you to access your other services via the domain name while still gaining the benefits of using a cdn.
Now I know you could use an 'ftp' subdomain or the like, but to each their own in that regard.7
A Timehop from 3 years ago stated "I will learn one day to do 301 redirects in .htaccess without Googling it."
I still don't know.2
"Must be 301 style for SEO benefits... "
So, hows your day going? 🤣🤣6
Developed a very simple REST api with pure php. Eventually "api/users/" worked but "api/users" was 301 moved!!.. it was a big problem1
First entry here. During my first internship, which was 6 years ago, the guy who was supposed to "supervise" me was developing a project and he had to create a json endpoint.
He was basically truncating&writing the data into a statically named file (data.json) and then redirecting the page to that file with http 301.
I had to simulate him concurrent requests to show him the possible confliction.
i received a job offer to work at area 51 on extremely sophisticated projects primarily as a c++ engineer. this is the highest pay offer i have ever seen, which i can not discuss right now, but what else to expect when you work for the government. i have bad perception about this. should i take this job or refuse?5
My monday while writing test:
[error] x should return 200 with no $path
[error] '301' is not equal to '404'