PHP 7.1 has many fans in the web developer community. But now it's time to say goodbye and switch to a newer version. The development team has set the end-of-life date for PHP 7.1 for the 1st of December, 2019. From that date on, the version will receive no further updates. Even security gaps will no longer be closed by the official developers. What should you do now?
Permanent availability is one of the most important things when it comes to a website. However, even the best technical conditions do not offer a 100% guarantee that a website will constantly run smoothly. Connection errors like HTTP error 408 regularly present websites with minor and major difficulties, especially since the causes are often found on the client side. Our guide looks at the causes...
Try and imagine a world where you don’t have to memorise passwords: Thanks to FIDO2, this could soon become a reality. Authentication in online shops or for online banking can be done through a fingerprint or hardware token. The latter can communicate with laptops of PCs through a USB, NFC or Bluetooth. To enable conversations between two devices, FIDO2 uses the Client to Authenticator Protocol...
Security support for PHP 5.6 ceases at the end of the year. Although developers had already postponed the end date by a year, many website operators still seem to be unprepared. A large number of websites still run on PHP 5.6. From January onwards, these websites will be at risk. However, many are dreading the update. How can you protect your website?
Out-dated technology can still be interesting. Even though the Reverse Address Resolution Protocol was introduced in 1984, and considered obsolete the following year due to the Bootstrap Protocol, it continued to be used long after. The RARP has not completely disappeared from network technology even today. As the Reverse ARP, this protocol is a counterpart to the Address Resolution Protocol. But...
Without the Domain Name System, users of the World Wide Web would have serious problems when trying to load websites and other online presences. It’s only thanks to this system that internet addresses appear in their trusted text format: they’re actually nothing more than combinations of numbers. The communication between browser and name server responsible for this isn’t actually as secure as you...
HTTP is indispensable as a mediator between the browser and web server: Both communicate with each other using the transmission protocol on the application layer by sending various types of messages. With an HTTP request, for example, the browser can request a resource or return its own data to the server. If one of these HTTP methods doesn’t work, error 405 (Method Not Allowed) occurs. But what...
If you want to send a message with your e-mail client and the sending fails, you’ll receive a corresponding error message from the server, including an SMTP status code. For example, the message “550 Requested action not taken: mailbox unavailable” means that the targeted address couldn’t be reached. Since this problem can have various causes, even more possible solutions exist, some of which you...
There are daily reports on how security gaps in applications are exploited – because hardly a day goes by without a new gap being discovered or a known gap being closed. One attack method, which has always been based on exploiting such weak points, is called SQL injection. But what is actually hidden behind the malicious database exploitation and how can you protect your database system from it?
Internet users are often confronted with error messages. HTTP status codes can be especially annoying, and even more so if you don’t understand what they mean. The message 'HTTP 400 – Bad Request' is a mystery for many internet users, but luckily it can be solved in most cases. We explain what the error message means and how to fix the error.
Provide powerful and reliable service to your clients with a web hosting package from IONOS
