Fixing wrong extensions

Around Thursday, April 7, 2016 5PM UTC time, I was adding ICO support to backend and testing ICO uploads when I noticed that every url upload returns jpg as the image extension for every image. this is the minor issue for users since modern browsers doesn't care about the image extensions, but there was a little issue since the image delivery system gets the image content type by the image extension. A fix was quickly applied as I was familiar with the function that misbehaved. so the uploads after should be fine.


But what about the images uploaded before the fix?
It was already night here, so I deiced to add the fix for those images the next day. since I will be touching the main scripts and raw images that powers the site and I don't want mess any of that.


Fast forward to today, I just shipped the extension correction to the system, but it will occur in batches. It there so that I can monitor if any thing goes wrong.


The extension correction will update the database so that image view page will get the correct extension. if the image is already shared with the wrong extension, a redirection pointer will be added so it will be redirected to the correct extension.


To find if you images were affected, click the image edit button in the image view page and you will see a notice like below.


image lgo


UPDATE: (Saturday, April 9, 2016 2PM UTC)


Extension correction is done, and 537 of images were affected. The extension redirection is working smoothly. I have added a new panel in the dashboard to view the images that were affected for the registered users.


Below are the full stats as a pie chart. Enjoy

Comments

Post a Comment

Popular posts from this blog

Stability Improvements 2020

Hi all, Since we detected that the site was operating in a degraded status causing increase rate of 500 server errors, we checked the servers and found the memory usage was high on all servers. To remedy that we upgraded the database server and rebooted all app servers clearing the memory on them and these steps reduced the error rate. Also we improved loading balancing and fail-over logic in the frontend servers. It is due to these improvements and improved thumb image caching, that we were able to release the search page to public. Earlier we constrained with less data and errors on creating thumbnail images on the results page. Please enjoy the improved service and please do reach us, if you find the service not fast enough. Thanks. Also read the stability improvements we did in 2019 in this post: https://blog.beeimg.com/2019/12/stability-improvements-2019.html
Read more

Stability Improvements 2019

Hello all, Over the past few weeks BeeIMG has been a little unstable and just wanted to clarify on what happened. In the first unstable issue which in November were caused by our server provider doing maintenance on our servers. Our AMS node got hanged up during the maintenance and had to be manually restarted. However the impact on the service was minimal and the maintenance on our CDG node affected our service as its where our databases is hosted. After the maintenance the db server had been moved to under performing hypervisor and started to slow down the site. We had to move the server again to a better server. Forward to December, one on of our free customers started hitting with lot of image view per second and this overloaded memory on AMS server and to redis node to fail. Making maters worse AMS server ran out of disk space. when a fail over to CDG happened the traffic overload that servers redis node and caused the service to fail. The site served 503 errors durin
Read more

Recent Hiccups May 2016

We faced some blackouts recently, and it was because we got very popular in china. The images that was generating lot of traffic were violating our TOS, but as they were generating lot of traffic and I thought it was a good time to stress test our image delivery systems. At first we were handling the load fine. after some time our redis server start acting wired. the issue was with dumping the db to disk, but as the images were generating lot of data the redis server crashed. we started to migrate the all gif images to be served by our CDN while still collecting views data. but at some point our real time stats handling script started to fail due to redis connection issues. after that the data started to collect and the redis server crashed every time it was started. While all that was happening we noticed that our php front end started throwing errors. this was due the connectivity issues to our redis server. The image serving end do not use redis server and was not afflicted. its usi
Read more