Apache Friends Support Forum

die WordPress 6.6 - das zweite Majorrelease - es wird bereits Mitte Juli erwartet:

die Arbeiten an der WordPress Version 6.6 - sie konzentrieren sich auf die folgende Bereiche

vorweg: hier einige Einblicke in den den Releasefahrplan der WordPress 6.6 https://make.wordpress.org/core/6-6/

An was wird momentan gearbeitet:

a. Das Managment der Layout wird überarbeitet: Auswirkungen auf Teile der Vorlagen & Muster (Patterns).
Das gesamte Management des Site-Editors wird bei WordPress 6.6 einer Überarbeitung unterzogen - ausgebaut und optimiert.
Der Fokus auf dem Ausbau der User-Experience bringt es mit sich, dass alle möglichen Tools des Editors, z.B. auch die Vorlagen selbst, darüber hinaus auch die Seitenverwaltung
überarbeitet wird. Die diversen Ansichten im Site-Editor, sie werden einer Optimierung unterzogen und werden weiterentwickelt - m.a.W. einige der Ansichten des Site-Editors werden einer Optimierung unterzogen. Unter anderem wird hier auch das Managment der Templates verbessert. Die Benutzerfreundlichkeit - sie ist eine wichtige Kategorie bei dieser Überarbietung. Es sollen die Möglichkeiten für die Darstellung der einzelnen Templates und Templateteile verbessert und verbreitert werden. Auf diese Weise soll die Benutzerfreundlichkeit gewinnen - und wesentlich verbessert werden. Das ganze Handling des Editors - des Layouts, die Verwaltung von Template und Templateteile wird hier vorangebracht und Verbesserungen unterzogen.

b. die Performance soll verbessert werden

Alle Updates und veröffentlichten Beta-Versionen kommen in den folgenden Wochen: Wir werden berichten - hier einige Infos zum Release Shedule:

das Beta 1 wird erwartet: 4. Juni
der Release Candidate 1: Ende Juni

Hier noch ein kurzes Video: Coming soon to WordPress 6.6 https://www.youtube.com/watch?v=g07vnQe084c

There's a handful of changes coming to WordPress 6.6, including updates to the UI/UX of the publishing workflow. In today's video, I'll show you what they have planned so far and how you can get involved.
Scheduled workflow discussion: https://github.com/WordPress/gutenberg
Test the nightly build: https://playground.wordpress.net

WordPress 6.6 will be the second major release of 2024
https://make.wordpress.org/core/6-6/

Release team:
Release Lead: Matt Mullenweg
Release Coordinator: Meher Bala
Core Tech Lead: Jb Audras
Editor Tech Leads: Ella van Durpe, Vicente Canales
Core Triage Leads: Olga Gleckler, Nazmul Hasan Robin
Editor Triage Leads: Fabian Kägy, Damon Cook
Marketing & Communications Lead: Mary Baum
Test Lead: Anne McCarthy
Design Lead: Rich Tabor
Performance Lead: Adam Silverstein
Documentation Leads: JuanMa Garrido, Jenny Dupuy, Josep Morán
All release decisions will ultimately be this release team’s to make and communicate while gathering input from the community.

Release Schedule:
29 March 2024 6.6 Pre-planning post.
5 March 2024 Alpha Begins. Trunk is open for business.
4 June 2024 Beta 1. From this point on, core contributors will focus on testing and fixing bugs discovered during beta testing. Begin writing Dev Notes and the About page (Slack archive, ZIP download).
11 June 2024 Beta 2. Test the beta release, fix bugs discovered during beta testing, and continue writing Dev Notes and the About page (Slack archive, ZIP download).
18 June 2024 Beta 3. Test the beta release, fix bugs discovered during beta testing, and continue writing Dev Notes and the About page (Slack archive, ZIP download).
25 June 2024 Release candidate 1. Publish the Field Guide with Dev Notes, commit the About page, begin drafting the release post, hard string freeze, and branch for the release. (Slack archive, ZIP download).
2 July 2024 Release candidate 2. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
9 July 2024 Release candidate 3. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
15 July 2024 Dry run for release of WordPress 6.6 and 24-hour code freeze (Slack archive).
16 July 2024 WordPress 6.6 is released (Slack archive, ZIP download)!

more infos - more sources: Videos von Anne McCarthy
https://www.youtube.com/@AnneMcCarthy

Hello Apache Friends Community,

I wanted to share my recent journey in optimizing my website's performance using PHP and MySQL. Over the past few months, I've implemented several techniques that have significantly improved my site's speed and efficiency. Here are some key steps I took:

Query Optimization: I started by analyzing my MySQL queries and identified the ones that were causing slowdowns. By using indexes and optimizing the SQL syntax, I was able to reduce the load times substantially.

Caching: Implementing caching mechanisms, such as memcached and opcode caching, helped reduce the server load and improved response times for frequently accessed data.

Code Refactoring: I reviewed and refactored my PHP code to follow best practices, eliminating redundant code and improving logic flow. This made the codebase cleaner and more efficient.

Database Normalization: Normalizing the database structure helped reduce redundancy and improved data integrity, which in turn made the queries faster and more reliable.

Using Prepared Statements: To enhance security and performance, I switched to using prepared statements for database interactions. This not only reduced the risk of SQL injection but also improved execution times.

These changes have made a noticeable difference in my website's performance. I'd love to hear your experiences and any additional tips you might have for optimizing PHP and MySQL performance.

Looking forward to your feedback!

Hi,

Just to notice:

Scope of support

Evaluate if your topic is in scope of support of our board. We don't want to provide...
[...]

...support for live, production or public accessible environments.
XAMPP is not configurated for such environments (default passwords, many activated and probably unnecessary modules, not tweaked for performance, scalability, stability or security). This board does have several entrys about hacked XAMPP installations because of using unprotected XAMPP installations in not supported environments. XAMPP don't want to fit every possible use case and there are other (also free) alternatives for such environments.

[...]
Source: [INFO] How to not fail getting help here (Linked as "Forum rules")

Hallo liebe Community,

WordPress 6.5 wurde veröffentlicht. Die neueste Version von WordPress (Codname Regiona) ist das erste Major-Release des Jahres kommt mit großen Neuerungen: Ein Schwerpunkt liegt hierbei auf dem Ausbau der Gestaltungsmöglichkeiten.

neu in WordPress 6.5: Schriftarten, neue APIs und auch die Performance wurde verbessert.

Was ist drin: Nun, die Schriftartenbibliothek wird euch ermöglichen, eure gewünschten Schriftarten hochzuladen oder eine Verbindung zu Google Fonts herzustellen, wodurch die Notwendigkeit entfällt, zusätzliche Plugins zu verwenden (wie es früher notwendig war), um dies zu erreichen die gleiche Funktionalität.

Harte Arbeit: Es war harte Arbeit: Viele Entwickler haben daran gearbeitet – und haben sich an den Diskussionen auf Github, Slack und anderswo beteiligt. Es war eine harte Arbeit
Die Schriftartenbibliothek wird jetzt in WordPress 6.5 kommen.

Die Schriftartenbibliothek in WordPress 6.5
Lange ersehnt und nun endlich verfügbar: Mit dem Release von WordPress 6.5 wird die Schriftartenbibliothek eingeführt. Ein Feature, das ursprünglich für WordPress 6.4 geplant war, jetzt aber seine Premiere feiert. Diese Neuerung vereinfacht das Arbeiten mit Schriften sehr stark - denn nun werden die Webfonts zentral verwaltet.

Verbesserter Gutenberg Editor
dem verbessertn Gutenberg Editor wurde viel Aufmerksamkeit geschenkt; Er hat nun einige neue (Gestaltungs-) Optionen bekommen - auch solche die das Blockdesign betreffen.
Das Arbeiten mit Farbvariationen in Blöcken wurde überarbeitet, die Gestaltung des Layouts insgesamt verbessert (z.B. durch den Einsatz von intuitiven Steuerelementen und Vorschaufunktionen)

Arbeit an APIs:
- Die Interaktivitäts-API sorgt für mehr kreative Optionen im Front-End,
- Block-Bindungs-API stellt neue dynamische Verbindungen zwischen Blöcken und Daten her.

mehr infos - mehr ganz aktuelle Einblicke in die Features:

Dave (core attendand tech lead ) CUSTOM FONTS finally unlock creative freedom in the WORDPRESS 6.5 Font Library
https://www.youtube.com/watch?v=jHDrWC4TFhw

What's New In WordPress 6.5? - Font Library, The Interactivity API, AVIF Image support and much more
https://www.youtube.com/watch?v=av6SMK15Tgo
The release of WordPress 6.5 is planned for March 2024. We are enthusiastic about this release, just like every other WordPress user and member of the community.

Exploring WordPress 6.5
https://www.youtube.com/watch?v=DtJwcJF9LM8
In this lesson, we will explore some new features that landed with WordPress 6.5.

WordPress and Notion: some ways and methods to interact

here we show you some options... - of interaction between the productivity-tool ( Notion.so ) and WordPress:

WP Sync for Notion – Notion to WordPress Von WP connect
https://de.wordpress.org/plugins/wp-sync-for-notion/
by https://wpconnect.co/

meta: Version:1.4.0 Zuletzt aktualisiert:vor 1 Monat Aktive Installationen:1.000+ WordPress-Version:5.7 oder höher Getestet bis:6.4.3 PHP-Version:7.0 oder höher Sprachen:Alle 2 anzeigen Schlagwörter:apiautomationnocodenotionwpconnect

description:
With our Notion to WordPress integration, WP Sync for Notion, you’ll be able to create beautiful websites and manage content directly from Notion, the best digital workplace no code tool! Our plugin can export and sync any Notion database, page and content to your website, without Zapier or Make.
Create databases and pages with structured data into Notion: WP Sync for Notion will push and sync data to WordPress, swiftly!
Pro Version with multiple advanced features is available.

Features
Connect Notion databases and pages
Connect WordPress to Notion databases & pages (Databases only available in Pro Version)
Set up and publish unlimited connections (Pro Version)
Display Notion data in any post type
Display Notion data in WordPress in any post type ; Article, Page, Custom Post Types, with Post Status and Author (CPT only available in Pro Version)
Map Notion database properties to WordPress fields : title, date, category, excerpt… and Custom Fields (Custom Fields only available in Pro Version)
ACF (Advanced Custom Fields) support in Pro+ version
Display your content as it is in Notion or customize it
Support of major Notion blocks for pages (Paragraph, Title, List, Table, Separator, Image…) but also columns and internal Properties of Notion pages (cover, icon, …)
Integrate easily your content with our CPT “Notion Content” (Pro Version only)
Display it by using our dedicated Gutenberg block or use shortcodes for Divi, Elementor or any Page Builder (Pro Version only)
Customize synchronization of your data
Trigger data sync automatically or manually (Limited in Free Version)
Select update frequency or instantly via a webhook (Pro Version only)
Set up synchronization method (add, update, delete)
How to unleash your plugin’s full potential?
Go to the WP Sync for Notion plugin page, click on “Add New” next to “Connections”.

Choose a name for your new connection.
Enter your Internal integration token (Available in your Notion’s integrations here).
Choose the source of your data. From one or more pages. You also have the possibility to include children’s pages.
Select the destination of your content.
Link the Notion fields with WordPress fields.
Choose the Sync Settings (Strategy and Trigger).
Publish the connection, and you’re done!
Tip: By pressing the „Sync Now“ button, you can synchronize your contents for the first time (even if you didn’t choose “Manual only” trigger).

CF7 to Notion
Von WP connect :: by https://wpconnect.co/
https://de.wordpress.org/plugins/add-on-cf7-for-notion/

meta: Version:1.2.0 Zuletzt aktualisiert:vor 4 Monaten Aktive Installationen:200+ WordPress-Version:5.7 oder höher Getestet bis:6.4.0 PHP-Version:7.0 oder höher Sprachen:Alle 2 anzeigen Schlagwörter:apicontactform7formsnotionwpconnec
description:
Connect the popular WordPress plugin Contact Form 7 to Notion. This add-on enables you to integrate Contact Form 7 forms so that when users submit a form entry, the entries get directly added to Notion. You can link any field type including custom fields and add information to your Notion database.

Features
Set up the connection with Notion
Some simple steps to follow (only once)
A new Notion tab shows up in your form settings
Choose the destination database you want
Make your Notion page visible to the integration
For each form, select the database where you want to send data
Map your Contact Form 7 fields with Notion
All major field types are supported
Select the corresponding database field for each form field
User-friendly and helpful plugin interface
Dropdown lists for instant visualization of mapped fields
Many tooltips to make things easier
How does it work? How to use it?
Create a form with at least an e-mail field (don’t forget the consent field)

Go to Notion tab and check the box “Add form submissions to your database” to activate the connection
Choose the Notion’s database in which the data should be added
Map the fields of your Contact Form 7 form with your Notion’s columns
Click on “Save settings”

Support: If you need support, open a ticket on the Support.

Troubleshooting: Make sure you have created your database and columns in Notion before linking them to your form fields. If you don’t see it, wait 1 minute. Your Notion elements are cached for 60 seconds for optimal performance.
Supported Fields: Title, Text, Number, URL, E-mail, Phone, Select, Multiple Select and Date

Embed Notion Pages
https://de.wordpress.org/plugins/embed-notion-pages/
Von Embed Notion Pages :: https://www.embednotionpages.com/
meta: Version:1.0.0 Zuletzt aktualisiert:vor 9 Monaten Aktive Installationen:200+ WordPress-Version:4.0 oder höher Getestet bis:6.2.4 PHP-Version:7.0 oder höher Sprache:English (US

Embed Notion Pages is a powerful tool that lets you harness the power of Notion and embed its pages into your own website. Create your content in Notion, grab the provided embed code, and seamlessly integrate beautifully updated pages onto your site. While Notion provides a fantastic platform for content creation, directing users to a public Notion domain may not provide the best user experience. Embed Notion Pages allows you to enjoy all the creative freedom Notion offers, customise your embed to match your brand, and let people experience it as part of your own website. Essentially, Embed Notion Pages amplifies your content presentation while maintaining the usability and simplicity of Notion. This plugin works with shortcodes. Simply generate your Notion page embed code on our website and use the shortcode on your desired WordPress page/post.

Usage; Create your Notion page embed on our website https://www.embednotionpages.com
Use the WordPress shortcode [notion id="your-embed-id"] from your embed on your desired WordPress page/post.

what is notion:
see more here: https://www.notion.so

what is notion:
https://www.youtube.com/watch?v=oTahLEX3NXo&t=58s

btw: see also TablePress a awesome tableplugin - that not integrates with Notion... but is very cool by the way.

TablePress:
https://de.wordpress.org/plugins/tablepress/
by tobias Bäthge https://tablepress.org/

meta: version:2.3 Zuletzt aktualisiert:vor 7 Stunden Aktive Installationen:800.000+ WordPress-Version:6.0 oder höher Getestet bis:6.5 PHP-Version:7.2 oder höher Sprachen:Alle 42 anzeigen Schlagwörter:csvexcelspreadsheettabletables

Mach deine Webseite besser: Mit funktionsreichen Tabellen, die deine Besucher lieben werden!
TablePress ist das beliebteste und am besten bewertete WordPress-Tabellen-Plugin.

Erstelle, bearbeite und verwalte ganz einfach schöne und moderne Datentabellen, egal ob klein oder groß!
Füge für deine Besucher Sortierung, seitenweises Blättern, eine Suchfunktion und mehr hinzu!
Verwende jeden Datentyp, füge Bilder, Links und sogar mathematische Formeln ein!
Importiere und exportiere Tabellen aus/in Excel-, CSV-, HTML- und JSON-Dateien oder -URLs.
Binde Tabellen mit dem Blockeditor oder Shortcodes in Beiträge, Seiten oder andere Bereiche deiner Website ein.
Und das alles ohne Programmierkenntnisse!
Noch mehr großartige Funktionen für dich und deine Seitenbesucher sowie priorisierter E-Mail-Support stehen mit einer Premium-Lizenz von TablePress zur Verfügung. Schau sie dir an!

Hello there,

I'm relatively new to web development and have recently set up a local development environment using XAMPP for PHP projects. While I've managed to get everything up and running smoothly, I'm beginning to notice some performance issues, particularly when handling larger datasets or running more complex scripts.

I've done some research on optimizing PHP performance, but I'm finding it challenging to navigate through the wealth of information available online. I'm reaching out to this community for some guidance on best practices or specific tweaks I can apply to my XAMPP setup to improve PHP performance.

Some specific questions I have include:

Are there any configuration settings within XAMPP or PHP itself that can help optimize performance?
Are there any recommended tools or plugins for monitoring and fine-tuning performance in a local development environment?

OBS Studio 30.1 Beta Released mit AV1 Support für VA-API & WebRTC/WHIP Output

neu auf OBSproject.com:

OBS Studio 30.1 Beta 1 is now available for testing! This update adds HDR support for YouTube over RTMP, a brand new Image Slideshow source, direct audio capture from the Game Capture and Window Capture sources on Windows, PipeWire capture device support, additional support for AV1, and more! Plus, our usual bug fixes, performance improvements, and small usability tweaks.

more infos & data: https://obsproject.com/forum/threads/ob ... ost-637553

did you ever hear about the leightweight linux overview:....

.... have you ever mused about a leightweight linux - for example DSL Dammned Small Linux -... here you can... DSL is back ...
The New DSL 2024 has been reborn as a compact Linux distribution tailored for low-spec x86 computers. It packs a lot of applications into a small package. All the applications are chosen for their functionality, small size, and low dependencies. DSL 2024 also has many text-based applications that make it handy to use in a term window or TTY. DSL 2024 currently only ships with two window managers: Fluxbox and JWM. Both are lightweight, fairly intuitive, and easy to use.

see more below.... ... and discuss your ideas with us.

whats your favorite !?

https://en.wikipedia.org/wiki/Light-wei ... stribution.

quote from Wikipedia: A light-weight Linux distribution is one that uses lower memory and/or has less processor-speed requirements than a more "feature-rich" Linux distribution. The lower demands on hardware ideally result in a more responsive machine, and/or allow devices with fewer system resources (e.g. older or embedded hardware) to be used productively. The lower memory and/or processor-speed requirements are achieved by avoiding software bloat, i.e. by leaving out features that are perceived to have little or no practical use or advantage, or for which there is no or low demand.
The perceived weight of a Linux distribution is strongly influenced by the desktop environment included with that distribution.Accordingly, many Linux distributions offer a choice of editions. For example, Canonical hosts several variants ("flavors") of the Ubuntu distribution that include desktop environments other than the default GNOME or the deprecated Unity. These variants include the Xubuntu and Lubuntu distributions for the comparatively light-weight Xfce and LXDE / LXQt desktop environments.
The demands that a desktop environment places on a system may be seen in a comparison of the minimum system requirements of Ubuntu 10.10 and Lubuntu 10.10 desktop editions, where the only significant difference between the two was their desktop environment. Ubuntu 10.10 included the Unity desktop, which had minimum system requirements of a 2 GHz processor with 2 GB of RAM,[3] while Lubuntu 10.10 included LXDE, which required at least a Pentium II with 128 MB of RAM.

Overview of some distributions:
Gentoo ( https://www.gentoo.org ) – can be the lightest system, because even GUI is not included, and can be compiled with -march=native.
ArchBang – ( https://archbang.org ) inspired by CrunchBang Linux but based on the Arch Linux distribution instead of Debian.
DammnedSmallLinux ( https://www.damnsmalllinux.org ): The New DSL 2024 has been reborn as a compact Linux distribution tailored for low-spec x86 computers.
DebianDog - ( debiandog.github.io ): Debian Live CD shaped after Puppy Linux. It is packaged with JWM and IceWM, or Openbox and Xfce. Debian structure and behaviour are untouched.[7][8]
Dog Linux: DebianDog von ( debiandog.github.io ): DebianDog is very small Debian Live CD shaped to look and act like Puppy Linux.
Debian structure and Debian behaviour are untouched and ...
LinuxConsole ( https://www.linuxconsole.org )- a lightweight system for old computers made to be easy for youth and casual users.
Parabola GNU/Linux-libre ( https://www.parabola.nu ) an Arch-based lightweight system endorsed by the Free Software Foundation.
postmarketOS ( https://postmarketos.org ) – a derivative of Alpine Linux designed primarily for smartphones ::
Puppy-Linux: https://oldforum.puppylinux.com :
SparkyLinux ( https://sparkylinux.org ): a lightweight system based on Debian: SparkyLinux is a GNU/Linux distribution based on the Debian GNU/Linux operating system. Forums:; https://forum.sparkylinux.org
Zorin OS ( https://zorin.com/os/ ) – also has "Zorin OS Lite" and "Zorin OS Education Lite" editions :: Zorin OS is the alternative to Windows and macOS designed to make your computer faster, more powerful, secure, and privacy-respecting.

.....see the leightweight linux overview cf. https://en.wikipedia.org/wiki/Light-wei ... stribution.

one word regarding Debian: well Debian is called to be light enough: It just depends on the desktop as to whether it is light enough for you.
A genuin Debian based distro will be roughly the same. But wait: Enough RAM and a proper SSD and Debian is perfectly fine even on 10+ year old hardware.
And with a genuin Debian - we can say everything works - every button, suspend, fingerprint.

conclusio: so some say that there's no need to switch to a "lightweight"-distro, because Debian can be configured to be as lightweight as well.
Debian itself is light enough. It just depends on the desktop as to whether it is light enough for many of us. A genuine Debian based distro will be roughly the same as a so called leightweight Distro.

damnsmalllinux: http://www.damnsmalllinux.org: https://en.wikipedia.org/wiki/Damn_Small_Linux: damnsmalllinux The New DSL 2024 has been reborn as a compact Linux distribution tailored for low-spec x86 computers. It packs a lot of applications into a small package. All the applications are chosen for their functionality, small size, and low dependencies. DSL 2024 also has many text-based applications that make it handy to use in a term window or TTY. DSL 2024 currently only ships with two window managers: Fluxbox and JWM. Both are lightweight, fairly intuitive, and easy to use.

and here some more and other examples.... some other (leightweight) distros here in more details - discussion:

ArchBang ( https://archbang.org ): is a simple live Archlinux based distribution using Openbox window manager. Website/Blog http://www.archbang.org.

Gentoo ( https://www.gentoo.org ) – can be the lightest system, because even GUI is not included, and can be compiled with -march=native.
additional note: gentoo and Linux-lite: a little comparison; well when we compare Gentoo Linux and Linux Lite, there may be a big recommendation for the Linux Lite system:
Well i guess that we can talk abou the question“What are the best Linux distributions for Xfce or another leightweight desktop?

antiX ( https://antixlinux.com ) antiX is a blistering fast, lightweight and awesome well featured easy to install systemd-free linux live CD
distribution based on Debian Stable for Intel-AMD x86 compatible systems. antiX offers users the “antiX Magic” in an environment suitable for
old and new computers. So don’t throw away that old computer yet! on of the best lightweight Linux distro that has got many cool things: for example the following:

- very very few hardware requirements
- very featureich apps and functionality
- it works justg out of the box functionality
- has got a bunch of useful apps and a great additional set of custom apps

well, i think antiX is one of the best options that’ll be content on a computer with very little resources. antiX, which uses the very very lean DE called IceWM together with the awesome Rox file manager: my friends told me that this is one of the lightest distros on earth and it ships with lots of apps, including both mainstream and lightweight ones, for virtually every desktop task - including development etc. etx.

BunsenLabs Linux ( https://www.bunsenlabs.org ): BunsenLabs Linux Boron is a distribution offering a light-weight and easily customizable Openbox desktop. The project is a community continuation of CrunchBang. BunsenLabs it is among the best lightweight Linux distros - and is released recently
- very very fast - with overwhelming performance
- has got a terrific Openbox window manager
- it run also on very very old 32-bit machines as well

the new Lightweight Distro BunsenLabs Linux Boron Is Here - Based on Debian Bookworm actually released on January 24, 2024
BunsenLabs Linux Boron distribution is now available for download based on the Debian GNU/Linux 12 “Bookworm” operating system series. Here’s what’s new!

crunchbang: When crunchbang ceased, two projects went forward: crunchbang++ and bunsenlabs: it's very light. well perhapy we can give it a go.
Crunchbangplusplus | Debian Based Minimal Linux Distro ( https://www.crunchbangplusplus.org ) Crunchbangplusplus | Debian Based Minimal Linux Distro“ Crunchbang++ is a awesome distro!
So, why aren't more people aware of this really good Linux distro? Crunchbang++ is lightweight, fun to use, and well designed
crunchbang++ it also exists and can consider which suits. My take would be that bunsenlabs has evolved a bit more; crunchbang++ is more similar to its predecessor.
but on the other handside: all these got very little to do with the distro itself and on the other handside much more to do with the DE.
well for example the xfce: we can take this on a old laptop - with having only real issue.

DammnedSmallLinux ( https://www.damnsmalllinux.org ): The New DSL 2024 has been reborn as a compact Linux distribution tailored for low-spec x86 computers. It packs a lot of applications into a small package. All the applications are chosen for their functionality, small size, and low dependencies. DSL 2024 also has many text-based applications that make it handy to use in a term window or TTY.

LinuxConsole.org ( https://www.linuxconsole.org ): A lighweight distribution for children: Software available. The complete list of libraries for both 32 and 64 bits is listed at packages/list-x86

Linuxliteos: ( https://www.linuxliteos.com/index.html ) The most important reason people chose Linux Lite is: the Linux Lite is very well known for being a awesome great distro for migrating Windows users - from the MicroSoft-World: what is good - what is nice: has got a long list of awesome features

Lubuntu ( https://lubuntu.me ): one of the best lightweight Linux distro for older machines
the good thing about this distro:
- basead on Ubuntu but much much more leightweight
- it comes packed with a bunch of nifty lightweight apps
- Compatible with the big big awesome Ubuntu repositories

Lubuntu now ships the most advanced desktop interface, using Qt technologies for rendering the widgets and the entire ecosystem (from the installer to the smallest parts).
The winning combination of Arc theme and the Papirus icons makes the new Lubuntu desktop easier to read and less cluttered. The symbolic icons and glyphs, now easier to recognise, added to sharp edges and vibrant colours, add visual dynamics without overwhelming the overall design.

- Emphasizes awesome and great stability and a good user-support
- Good-looking distro
- Impressive big range of apps

LXLE ( https://lxle.net ): LXLE is a lightweight version of Linux based on the Ubuntu LTS (long term support) release.
Like Lubuntu, LXLE uses the barebones LXDE desktop environment,
but as LTS releases are supported for five years, it emphasizes stability and long-term hardware support.
The distro uses its own repos together with that of big and very very well known Debian’s. It bundles the Synaptic package manager,

Full featured OS for an aging PC.
LXLE Focal Now Available!
Light on resources; Heavy on functions.
Always based on Ubuntu/Lubuntu LTS.
Uses an optimized LXDE user interface.
Simple, Elegant and Familiar desktop UI.
Prudent full featured Apps preinstalled.
Latest stable versions of all major apps.
Added PPAs extends available software.
Expose, Aero Snap, Quick Launch apps
Random & Interval Wallpaper Changer

postmarketOS ( https://postmarketos.org ) – a derivative of Alpine Linux designed primarily for smartphones :: We are sick of not receiving updates shortly after buying new phones. Sick of the walled gardens deeply integrated into Android and iOS. That's why we are developing a sustainable, privacy and security focused free software mobile OS that is modeled after traditional Linux distributions. With privilege separation in mind. Let's keep our devices useful and safe until they physically break!

parabola.nu: ( https://www.parabola.nu ) : You've reached the website of Parabola GNU/Linux-libre. The Parabola project is a community-driven, "labour-of-love" effort to maintain a 100% free (as in: freedom) operating system distribution that is lean, clean, and hackable. Based on the Arch distribution, Parabola is a complete, user-friendly operating system, suitable for general "everyday" use, while retaining Arch's "power-user" charm. Parabola adheres to the GNU Free System Distribution Guidelines (FSDG); which requires source code for every part of the system to be freely available, modifyable, and re-distributable. All Parabola packages are built from source, in clean chroots, and with networking disabled, in order to replace any software and artworks in the standard Arch system which fall outside the GNU guidelines. LiveISOs, installers, and packages are provided for the armv7h, i686, and x86_64 CPU architectures.

and discuss your ideas with us.

whats your favorite !?

plonkarchivist wrote:It appears that you are experiencing challenges with the recent versions of the software, particularly with the MySQL database service randomly ceasing to function. Despite installing the latest version, the performance remains inconsistent, alternating between working and failing. The puzzle lies in understanding the underlying reasons for these spontaneous breakdowns and disruptions. Although various solutions have been proposed, the fundamental cause remains elusive. Investigating the root cause may be essential to resolving the issue comprehensively.

Absolutely right! Last year I installed version 8.1.1.2. Not working!!! This year I installed 8.2.12, worked for 2 days. A dance began with tambourines around the database service MySQL that suddenly stopped working. You'll have to switch to another server.

What lightweight linux distro do you recommend for a older Hardware !?`

I'm considering to run a very very leight Linux because my current Notebook is really poor. The LENOVO T 520 has got not too much RAM: i want to run a lieightweight Linux: I would also prefer one with a good GUI but I don't really care much as long I'll my Lenovo Thinkpad T520 has got 4GBs of ram and a 320gb HDD.

i have heard about the leightweight linux overview: leightweight linux overview

https://en.wikipedia.org/wiki/Light-wei ... stribution.

A light-weight Linux distribution is one that uses lower memory and/or has less processor-speed requirements than a more "feature-rich" Linux distribution. The lower demands on hardware ideally result in a more responsive machine, and/or allow devices with fewer system resources (e.g. older or embedded hardware) to be used productively. The lower memory and/or processor-speed requirements are achieved by avoiding software bloat, i.e. by leaving out features that are perceived to have little or no practical use or advantage, or for which there is no or low demand.

The perceived weight of a Linux distribution is strongly influenced by the desktop environment included with that distribution.[1][2] Accordingly, many Linux distributions offer a choice of editions. For example, Canonical hosts several variants ("flavors") of the Ubuntu distribution that include desktop environments other than the default GNOME or the deprecated Unity. These variants include the Xubuntu and Lubuntu distributions for the comparatively light-weight Xfce and LXDE / LXQt desktop environments.

The demands that a desktop environment places on a system may be seen in a comparison of the minimum system requirements of Ubuntu 10.10 and Lubuntu 10.10 desktop editions, where the only significant difference between the two was their desktop environment. Ubuntu 10.10 included the Unity desktop, which had minimum system requirements of a 2 GHz processor with 2 GB of RAM,[3] while Lubuntu 10.10 included LXDE, which required at least a Pentium II with 128 MB of RAM.[4]

Overview of some distributions

and for example....
antiX
on of the best lightweight Linux distro that’

+ very very few hardware requirements
+ it works justg out of the box functionality
+ has got a bunch of useful apps and a great additional set of custom apps

well i think antiX is one of the best options that’ll be content on a computer with very little resources.
antiX, which uses IceWM together with the Rox file manager,
my friends told me that this is one of the lightest distros on earth and it ships with lots of apps,
including both mainstream and lightweight ones, for virtually every desktop task - including development etc. etx.

BunsenLabs
it is among the best lightweight Linux distros - and is released recently

+very very fast - with overwhelming performance
+ has got a terrific Openbox window manager
+ it run also on 32-bit machines as well

see Lightweight Distro BunsenLabs Linux Boron Is Here Based on Debian Bookworm -- January 24, 2024
BunsenLabs Linux Boron distribution is now available for download based on the Debian GNU/Linux 12 “Bookworm” operating system series. Here’s what’s new!

see more leightweight linux overview
https://en.wikipedia.org/wiki/Light-wei ... stribution.

a lightweight linux distro for a older Hardware ideas...!? - what would you recommend?

Hello dear community

Is it possible to split a database or table over several hard disks? The database is growing relatively quickly. Now I might need another or larger hard disk. Is it possible to split the database onto several HDDs or SSDs?

If so, does this result in a performance boost or performance problems?

Thanks

Nobbie wrote:Ok, there is LISTEN 4434.

Look into xampp-control.ini and see if you also changed "ApacheSSL" to 4434. If its still set to 443, change it to 4434 and restart Xampp Control Dialog. Then try again.

But last not least, i think you have multiple Apaches on your Server and starting the "wrong" one.

Sorry for the late reply.

So i did the following.
STOP THE APACHE EN MYSQL services
current xampp folder in E:\xampp i have renamed the name Apache and php to -old both.
Then i extract the version i want to use, and copied the Apache and php in to the e:\xampp folder
then in php folder php.ini file i have changed the \xampp all of them to e:\xampp\xx\xx
then ApacheSSL en the xampp apache.control.ini file changed it to 4434

Code: Select all: [Common] Edition= Editor=C:\Program Files\Notepad++\notepad++.exe Browser=C:\Program Files\Google\Chrome\Application\chrome.exe Debug=0 Debuglevel=0 TomcatVisible=0 Language=en Minimized=0 [EnableModules] Apache=1 MySQL=1 FileZilla=0 Mercury=0 Tomcat=1 [LogSettings] Font=Arial FontSize=10 [WindowSettings] Left=138 Top=31 Width=1146 Height=495 [Autostart] Apache=0 MySQL=0 FileZilla=0 Mercury=0 Tomcat=0 [Checks] CheckRuntimes=1 CheckDefaultPorts=1 [ModuleNames] Apache=Apache MySQL=MySQL FileZilla=FileZilla Mercury=Mercury Tomcat=Tomcat [EnableServices] Apache=1 MySQL=1 FileZilla=1 Tomcat=1 [BinaryNames] Apache=httpd.exe MySQL=mysqld.exe FileZilla=filezillaserver.exe FileZillaAdmin=filezilla server interface.exe Mercury=mercury.exe Tomcat=tomcat8.exe [ServiceNames] Apache=Apache2.4 MySQL=mysql FileZilla=FileZillaServer Tomcat=Tomcat [ServicePorts] Apache=80 ApacheSSL=4434 MySQL=3306 FileZilla=21 FileZillaAdmin=14147 Mercury1=25 Mercury2=79 Mercury3=105 Mercury4=106 Mercury5=110 Mercury6=143 Mercury7=2224 TomcatHTTP=8080 TomcatAJP=8009 Tomcat=8005 [UserConfigs] Apache= MySQL= FileZilla= Mercury= Tomcat= [UserLogs] Apache= MySQL= FileZilla= Mercury= Tomcat=

httpd

Code: Select all: # # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See <URL:http://httpd.apache.org/docs/2.4/> for detailed information. # In particular, see # <URL:http://httpd.apache.org/docs/2.4/mod/directives.html> # for a discussion of each configuration directive. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "logs/access_log" # with ServerRoot set to "/usr/local/apache2" will be interpreted by the # server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log" # will be interpreted as '/logs/access_log'. # # NOTE: Where filenames are specified, you must use forward slashes # instead of backslashes (e.g., "c:/apache" instead of "c:\apache"). # If a drive letter is omitted, the drive on which httpd.exe is located # will be used by default. It is recommended that you always supply # an explicit drive letter in absolute paths to avoid confusion. # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # Do not add a slash at the end of the directory path. If you point # ServerRoot at a non-local disk, be sure to specify a local disk on the # Mutex directive, if file-based mutexes are used. If you wish to share the # same ServerRoot for multiple httpd daemons, you will need to change at # least PidFile. # Define SRVROOT "/xampp/apache" ServerRoot "/xampp/apache" # # Mutex: Allows you to set the mutex mechanism and mutex file directory # for individual mutexes, or change the global defaults # # Uncomment and change the directory if mutexes are file-based and the default # mutex file directory is not on a local disk or is not appropriate for some # other reason. # # Mutex default:logs # # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, instead of the default. See also the <VirtualHost> # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses. # #Listen 12.34.56.78:80 Listen 80 # # Dynamic Shared Object (DSO) Support # # To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule' lines at this location so the # directives contained in it are actually available _before_ they are used. # Statically compiled modules (those listed by `httpd -l') do not need # to be loaded here. # # Example: # LoadModule foo_module modules/mod_foo.so # LoadModule access_compat_module modules/mod_access_compat.so LoadModule actions_module modules/mod_actions.so LoadModule alias_module modules/mod_alias.so LoadModule allowmethods_module modules/mod_allowmethods.so LoadModule asis_module modules/mod_asis.so LoadModule auth_basic_module modules/mod_auth_basic.so #LoadModule auth_digest_module modules/mod_auth_digest.so #LoadModule auth_form_module modules/mod_auth_form.so #LoadModule authn_anon_module modules/mod_authn_anon.so LoadModule authn_core_module modules/mod_authn_core.so #LoadModule authn_dbd_module modules/mod_authn_dbd.so #LoadModule authn_dbm_module modules/mod_authn_dbm.so LoadModule authn_file_module modules/mod_authn_file.so #LoadModule authn_socache_module modules/mod_authn_socache.so #LoadModule authnz_fcgi_module modules/mod_authnz_fcgi.so #LoadModule authnz_ldap_module modules/mod_authnz_ldap.so LoadModule authz_core_module modules/mod_authz_core.so #LoadModule authz_dbd_module modules/mod_authz_dbd.so #LoadModule authz_dbm_module modules/mod_authz_dbm.so LoadModule authz_groupfile_module modules/mod_authz_groupfile.so LoadModule authz_host_module modules/mod_authz_host.so #LoadModule authz_owner_module modules/mod_authz_owner.so LoadModule authz_user_module modules/mod_authz_user.so LoadModule autoindex_module modules/mod_autoindex.so #LoadModule brotli_module modules/mod_brotli.so #LoadModule buffer_module modules/mod_buffer.so #LoadModule cache_module modules/mod_cache.so #LoadModule cache_disk_module modules/mod_cache_disk.so #LoadModule cache_socache_module modules/mod_cache_socache.so #LoadModule cern_meta_module modules/mod_cern_meta.so LoadModule cgi_module modules/mod_cgi.so #LoadModule charset_lite_module modules/mod_charset_lite.so #LoadModule data_module modules/mod_data.so #LoadModule dav_module modules/mod_dav.so #LoadModule dav_fs_module modules/mod_dav_fs.so LoadModule dav_lock_module modules/mod_dav_lock.so #LoadModule dbd_module modules/mod_dbd.so #LoadModule deflate_module modules/mod_deflate.so LoadModule dir_module modules/mod_dir.so #LoadModule dumpio_module modules/mod_dumpio.so LoadModule env_module modules/mod_env.so #LoadModule expires_module modules/mod_expires.so #LoadModule ext_filter_module modules/mod_ext_filter.so #LoadModule file_cache_module modules/mod_file_cache.so #LoadModule filter_module modules/mod_filter.so #LoadModule http2_module modules/mod_http2.so LoadModule headers_module modules/mod_headers.so #LoadModule heartbeat_module modules/mod_heartbeat.so #LoadModule heartmonitor_module modules/mod_heartmonitor.so #LoadModule ident_module modules/mod_ident.so #LoadModule imagemap_module modules/mod_imagemap.so LoadModule include_module modules/mod_include.so LoadModule info_module modules/mod_info.so LoadModule isapi_module modules/mod_isapi.so #LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so #LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so #LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so #LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so #LoadModule ldap_module modules/mod_ldap.so #LoadModule logio_module modules/mod_logio.so LoadModule log_config_module modules/mod_log_config.so #LoadModule log_debug_module modules/mod_log_debug.so #LoadModule log_forensic_module modules/mod_log_forensic.so #LoadModule lua_module modules/mod_lua.so LoadModule cache_disk_module modules/mod_cache_disk.so #LoadModule macro_module modules/mod_macro.so #LoadModule md_module modules/mod_md.so LoadModule mime_module modules/mod_mime.so #LoadModule mime_magic_module modules/mod_mime_magic.so LoadModule negotiation_module modules/mod_negotiation.so LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_ajp_module modules/mod_proxy_ajp.so #LoadModule proxy_balancer_module modules/mod_proxy_balancer.so #LoadModule proxy_connect_module modules/mod_proxy_connect.so #LoadModule proxy_express_module modules/mod_proxy_express.so #LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so #LoadModule proxy_hcheck_module modules/mod_proxy_hcheck.so #LoadModule proxy_html_module modules/mod_proxy_html.so #LoadModule proxy_http_module modules/mod_proxy_http.so #LoadModule proxy_http2_module modules/mod_proxy_http2.so #LoadModule proxy_scgi_module modules/mod_proxy_scgi.so #LoadModule proxy_uwsgi_module modules/mod_proxy_uwsgi.so #LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so #LoadModule ratelimit_module modules/mod_ratelimit.so #LoadModule reflector_module modules/mod_reflector.so #LoadModule remoteip_module modules/mod_remoteip.so #LoadModule request_module modules/mod_request.so #LoadModule reqtimeout_module modules/mod_reqtimeout.so LoadModule rewrite_module modules/mod_rewrite.so #LoadModule sed_module modules/mod_sed.so #LoadModule session_module modules/mod_session.so #LoadModule session_cookie_module modules/mod_session_cookie.so #LoadModule session_crypto_module modules/mod_session_crypto.so #LoadModule session_dbd_module modules/mod_session_dbd.so LoadModule setenvif_module modules/mod_setenvif.so #LoadModule slotmem_plain_module modules/mod_slotmem_plain.so #LoadModule slotmem_shm_module modules/mod_slotmem_shm.so #LoadModule socache_dbm_module modules/mod_socache_dbm.so #LoadModule socache_memcache_module modules/mod_socache_memcache.so #LoadModule socache_redis_module modules/mod_socache_redis.so LoadModule socache_shmcb_module modules/mod_socache_shmcb.so #LoadModule speling_module modules/mod_speling.so LoadModule ssl_module modules/mod_ssl.so LoadModule status_module modules/mod_status.so #LoadModule substitute_module modules/mod_substitute.so #LoadModule unique_id_module modules/mod_unique_id.so #LoadModule userdir_module modules/mod_userdir.so #LoadModule usertrack_module modules/mod_usertrack.so #LoadModule version_module modules/mod_version.so #LoadModule vhost_alias_module modules/mod_vhost_alias.so #LoadModule watchdog_module modules/mod_watchdog.so #LoadModule xml2enc_module modules/mod_xml2enc.so <IfModule unixd_module> # # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # # User/Group: The name (or #number) of the user/group to run httpd as. # It is usually good practice to create a dedicated user and group for # running httpd, as with most system services. # User daemon Group daemon </IfModule> # 'Main' server configuration # # The directives in this section set up the values used by the 'main' # server, which responds to any requests that aren't handled by a # <VirtualHost> definition. These values also provide defaults for # any <VirtualHost> containers you may define later in the file. # # All of these directives may appear inside <VirtualHost> containers, # in which case these default settings will be overridden for the # virtual host being defined. # # # ServerAdmin: Your address, where problems with the server should be # e-mailed. This address appears on some server-generated pages, such # as error documents. e.g. admin@your-domain.com # ServerAdmin postmaster@localhost # # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If your host doesn't have a registered DNS name, enter its IP address here. # ServerName localhost:80 # # Deny access to the entirety of your server's filesystem. You must # explicitly permit access to web content directories in other # <Directory> blocks below. # <Directory /> AllowOverride none Require all denied </Directory> # # Note that from this point forward you must specifically allow # particular features to be enabled - so if something's not working as # you might expect, make sure that you have specifically enabled it # below. # # # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # DocumentRoot "/xampp/htdocs" <Directory "/xampp/htdocs"> # # Possible values for the Options directive are "None", "All", # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that "MultiViews" must be named *explicitly* --- "Options All" # doesn't give it to you. # # The Options directive is both complicated and important. Please see # http://httpd.apache.org/docs/2.4/mod/core.html#options # for more information. # Options Indexes FollowSymLinks Includes ExecCGI # # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords: # AllowOverride FileInfo AuthConfig Limit # AllowOverride All # # Controls who can get stuff from this server. # Require all granted </Directory> # # DirectoryIndex: sets the file that Apache will serve if a directory # is requested. # <IfModule dir_module> DirectoryIndex index.php index.pl index.cgi index.asp index.shtml index.html index.htm \ default.php default.pl default.cgi default.asp default.shtml default.html default.htm \ home.php home.pl home.cgi home.asp home.shtml home.html home.htm </IfModule> # # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <Files ".ht*"> Require all denied </Files> # # ErrorLog: The location of the error log file. # If you do not specify an ErrorLog directive within a <VirtualHost> # container, error messages relating to that virtual host will be # logged here. If you *do* define an error logfile for a <VirtualHost> # container, that host's errors will be logged there and not here. # ErrorLog "logs/error.log" # # LogLevel: Control the number of messages logged to the error_log. # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. # LogLevel warn <IfModule log_config_module> # # The following directives define some format nicknames for use with # a CustomLog directive (see below). # LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%h %l %u %t \"%r\" %>s %b" common <IfModule logio_module> # You need to enable mod_logio.c to use %I and %O LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio </IfModule> # # The location and format of the access logfile (Common Logfile Format). # If you do not define any access logfiles within a <VirtualHost> # container, they will be logged here. Contrariwise, if you *do* # define per-<VirtualHost> access logfiles, transactions will be # logged therein and *not* in this file. # #CustomLog "logs/access.log" common # # If you prefer a logfile with access, agent, and referer information # (Combined Logfile Format) you can use the following directive. # CustomLog "logs/access.log" combined </IfModule> <IfModule alias_module> # # Redirect: Allows you to tell clients about documents that used to # exist in your server's namespace, but do not anymore. The client # will make a new request for the document at its new location. # Example: # Redirect permanent /foo http://www.example.com/bar # # Alias: Maps web paths into filesystem paths and is used to # access content that does not live under the DocumentRoot. # Example: # Alias /webpath /full/filesystem/path # # If you include a trailing / on /webpath then the server will # require it to be present in the URL. You will also likely # need to provide a <Directory> section to allow access to # the filesystem path. # # ScriptAlias: This controls which directories contain server scripts. # ScriptAliases are essentially the same as Aliases, except that # documents in the target directory are treated as applications and # run by the server when requested rather than as documents sent to the # client. The same rules about trailing "/" apply to ScriptAlias # directives as to Alias. # ScriptAlias /cgi-bin/ "/xampp/cgi-bin/" </IfModule> <IfModule cgid_module> # # ScriptSock: On threaded servers, designate the path to the UNIX # socket used to communicate with the CGI daemon of mod_cgid. # #Scriptsock cgisock </IfModule> # # "/xampp/cgi-bin" should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # <Directory "/xampp/cgi-bin"> AllowOverride All Options None Require all granted </Directory> <IfModule headers_module> # # Avoid passing HTTP_PROXY environment to CGI's on this or any proxied # backend servers which have lingering "httpoxy" defects. # 'Proxy' request header is undefined by the IETF, not listed by IANA # RequestHeader unset Proxy early </IfModule> <IfModule mime_module> # # TypesConfig points to the file containing the list of mappings from # filename extension to MIME-type. # TypesConfig conf/mime.types # # AddType allows you to add to or override the MIME configuration # file specified in TypesConfig for specific file types. # #AddType application/x-gzip .tgz # # AddEncoding allows you to have certain browsers uncompress # information on the fly. Note: Not all browsers support this. # #AddEncoding x-compress .Z #AddEncoding x-gzip .gz .tgz # # If the AddEncoding directives above are commented-out, then you # probably should define those extensions to indicate media types: # AddType application/x-compress .Z AddType application/x-gzip .gz .tgz # # AddHandler allows you to map certain file extensions to "handlers": # actions unrelated to filetype. These can be either built into the server # or added with the Action directive (see below) # # To use CGI scripts outside of ScriptAliased directories: # (You will also need to add "ExecCGI" to the "Options" directive.) # AddHandler cgi-script .cgi .pl .asp # For type maps (negotiated resources): #AddHandler type-map var # # Filters allow you to process content before it is sent to the client. # # To parse .shtml files for server-side includes (SSI): # (You will also need to add "Includes" to the "Options" directive.) # AddType text/html .shtml AddOutputFilter INCLUDES .shtml </IfModule> # # The mod_mime_magic module allows the server to use various hints from the # contents of the file itself to determine its type. The MIMEMagicFile # directive tells the module where the hint definitions are located. # <IfModule mime_magic_module> # # The mod_mime_magic module allows the server to use various hints from the # contents of the file itself to determine its type. The MIMEMagicFile # directive tells the module where the hint definitions are located. # MIMEMagicFile "conf/magic" </IfModule> # # Customizable error responses come in three flavors: # 1) plain text 2) local redirects 3) external redirects # # Some examples: #ErrorDocument 500 "The server made a boo boo." #ErrorDocument 404 /missing.html #ErrorDocument 404 "/cgi-bin/missing_handler.pl" #ErrorDocument 402 http://www.example.com/subscription_info.html # # # MaxRanges: Maximum number of Ranges in a request before # returning the entire resource, or one of the special # values 'default', 'none' or 'unlimited'. # Default setting is to accept 200 Ranges. #MaxRanges unlimited # # EnableMMAP and EnableSendfile: On systems that support it, # memory-mapping or the sendfile syscall may be used to deliver # files. This usually improves server performance, but must # be turned off when serving from networked-mounted # filesystems or if support for these functions is otherwise # broken on your system. # Defaults: EnableMMAP On, EnableSendfile Off # #EnableMMAP off #EnableSendfile off # Supplemental configuration # # The configuration files in the conf/extra/ directory can be # included to add extra features or to modify the default configuration of # the server, or you may simply copy their contents here and change as # necessary. # Server-pool management (MPM specific) Include conf/extra/httpd-mpm.conf # Multi-language error messages #Include conf/extra/httpd-multilang-errordoc.conf # Fancy directory listings Include conf/extra/httpd-autoindex.conf # Language settings Include conf/extra/httpd-languages.conf # User home directories Include conf/extra/httpd-userdir.conf # Real-time info on requests and configuration Include conf/extra/httpd-info.conf # Virtual hosts Include conf/extra/httpd-vhosts.conf # Local access to the Apache HTTP Server Manual #Include conf/extra/httpd-manual.conf # Distributed authoring and versioning (WebDAV) #Attention! WEB_DAV is a security risk without a new userspecific configuration for a secure authentifcation #Include conf/extra/httpd-dav.conf # Various default settings #Include conf/extra/httpd-default.conf # Implements a proxy/gateway for Apache. Include "conf/extra/httpd-proxy.conf" # Various default settings Include "conf/extra/httpd-default.conf" # XAMPP settings Include "conf/extra/httpd-xampp.conf" # Configure mod_proxy_html to understand HTML4/XHTML1 <IfModule proxy_html_module> Include conf/extra/proxy-html.conf </IfModule> # Secure (SSL/TLS) connections Include conf/extra/httpd-ssl.conf # # Note: The following must must be present to support # starting without SSL on platforms with no /dev/random equivalent # but a statically compiled-in mod_ssl. # <IfModule ssl_module> SSLRandomSeed startup builtin SSLRandomSeed connect builtin </IfModule> # XAMPP: We disable operating system specific optimizations for a listening # socket by the http protocol here. IE 64 bit make problems without this. AcceptFilter http none AcceptFilter https none # AJP13 Proxy <IfModule mod_proxy.c> <IfModule mod_proxy_ajp.c> Include "conf/extra/httpd-ajp.conf" </IfModule> </IfModule>

https-ssl

Code: Select all: # # This is the Apache server configuration file providing SSL support. # It contains the configuration directives to instruct the server how to # serve pages over an https connection. For detailed information about these # directives see <URL:http://httpd.apache.org/docs/2.4/mod/mod_ssl.html> # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # Required modules: mod_log_config, mod_setenvif, mod_ssl, # socache_shmcb_module (for default value of SSLSessionCache) # # Pseudo Random Number Generator (PRNG): # Configure one or more sources to seed the PRNG of the SSL library. # The seed data should be of good random quality. # WARNING! On some platforms /dev/random blocks if not enough entropy # is available. This means you then cannot use the /dev/random device # because it would lead to very long connection times (as long as # it requires to make more entropy available). But usually those # platforms additionally provide a /dev/urandom device which doesn't # block. So, if available, use this one instead. Read the mod_ssl User # Manual for more details. # #SSLRandomSeed startup file:/dev/random 512 #SSLRandomSeed startup file:/dev/urandom 512 #SSLRandomSeed connect file:/dev/random 512 #SSLRandomSeed connect file:/dev/urandom 512 # # When we also provide SSL we have to listen to the # standard HTTP port (see above) and to the HTTPS port # Listen 4434 ## ## SSL Global Context ## ## All SSL configuration in this context applies both to ## the main server and all SSL-enabled virtual hosts. ## # SSL Cipher Suite: # List the ciphers that the client is permitted to negotiate, # and that httpd will negotiate as the client of a proxied server. # See the OpenSSL documentation for a complete list of ciphers, and # ensure these follow appropriate best practices for this deployment. # httpd 2.2.30, 2.4.13 and later force-disable aNULL, eNULL and EXP ciphers, # while OpenSSL disabled these by default in 0.9.8zf/1.0.0r/1.0.1m/1.0.2a. SSLCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES SSLProxyCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES # By the end of 2016, only TLSv1.2 ciphers should remain in use. # Older ciphers should be disallowed as soon as possible, while the # kRSA ciphers do not offer forward secrecy. These changes inhibit # older clients (such as IE6 SP2 or IE8 on Windows XP, or other legacy # non-browser tooling) from successfully connecting. # # To restrict mod_ssl to use only TLSv1.2 ciphers, and disable # those protocols which do not support forward secrecy, replace # the SSLCipherSuite and SSLProxyCipherSuite directives above with # the following two directives, as soon as practical. # SSLCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA # SSLProxyCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA # User agents such as web browsers are not configured for the user's # own preference of either security or performance, therefore this # must be the prerogative of the web server administrator who manages # cpu load versus confidentiality, so enforce the server's cipher order. SSLHonorCipherOrder on # SSL Protocol support: # List the protocol versions which clients are allowed to connect with. # Disable SSLv3 by default (cf. RFC 7525 3.1.1). TLSv1 (1.0) should be # disabled as quickly as practical. By the end of 2016, only the TLSv1.2 # protocol or later should remain in use. SSLProtocol all -SSLv3 SSLProxyProtocol all -SSLv3 # Pass Phrase Dialog: # Configure the pass phrase gathering process. # The filtering dialog program (`builtin' is an internal # terminal dialog) has to provide the pass phrase on stdout. SSLPassPhraseDialog builtin # Inter-Process Session Cache: # Configure the SSL Session Cache: First the mechanism # to use and second the expiring timeout (in seconds). #SSLSessionCache "shmcb:/xampp/apache/logs/ssl_scache(512000)" SSLSessionCache "shmcb:/xampp/apache/logs/ssl_scache(512000)" SSLSessionCacheTimeout 300 # OCSP Stapling (requires OpenSSL 0.9.8h or later) # # This feature is disabled by default and requires at least # the two directives SSLUseStapling and SSLStaplingCache. # Refer to the documentation on OCSP Stapling in the SSL/TLS # How-To for more information. # # Enable stapling for all SSL-enabled servers: #SSLUseStapling On # Define a relatively small cache for OCSP Stapling using # the same mechanism that is used for the SSL session cache # above. If stapling is used with more than a few certificates, # the size may need to be increased. (AH01929 will be logged.) #SSLStaplingCache "shmcb:${SRVROOT}/logs/ssl_stapling(32768)" # Seconds before valid OCSP responses are expired from the cache #SSLStaplingStandardCacheTimeout 3600 # Seconds before invalid OCSP responses are expired from the cache #SSLStaplingErrorCacheTimeout 600 ## ## SSL Virtual Host Context ## <VirtualHost _default_:443> # General setup for the virtual host DocumentRoot "/xampp/htdocs" ServerName www.example.com:443 ServerAdmin admin@example.com ErrorLog "/xampp/apache/logs/error.log" TransferLog "/xampp/apache/logs/access.log" # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on # Server Certificate: # Point SSLCertificateFile "conf/ssl.crt/server.crt" # the certificate is encrypted, then you will be prompted for a # pass phrase. Note that a kill -HUP will prompt again. Keep # in mind that if you have both an RSA and a DSA certificate you # can configure both in parallel (to also allow the use of DSA # ciphers, etc.) # Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt) # require an ECC certificate which can also be configured in # parallel. SSLCertificateFile "conf/ssl.crt/server.crt" #SSLCertificateFile "conf/ssl.crt/server.crt" #SSLCertificateFile "conf/ssl.crt/server.crt" # Server Private Key: # If the key is not combined with the certificate, use this # directive to point at the key file. Keep in mind that if # you've both a RSA and a DSA private key you can configure # both in parallel (to also allow the use of DSA ciphers, etc.) # ECC keys, when in use, can also be configured in parallel SSLCertificateKeyFile "conf/ssl.key/server.key" #SSLCertificateKeyFile "conf/ssl.key/server.key" #SSLCertificateKeyFile "conf/ssl.key/server.key" # Server Certificate Chain: # Point SSLCertificateChainFile at a file containing the # concatenation of PEM encoded CA certificates which form the # certificate chain for the server certificate. Alternatively # the referenced file can be the same as SSLCertificateFile "conf/ssl.crt/server.crt" # certificate for convenience. #SSLCertificateChainFile "${SRVROOT}/conf/server-ca.crt" # Certificate Authority (CA): # Set the CA certificate verification path where to find CA # certificates for client authentication or alternatively one # huge file containing all of them (file must be PEM encoded) # Note: Inside SSLCACertificatePath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCACertificatePath "${SRVROOT}/conf/ssl.crt" #SSLCACertificateFile "${SRVROOT}/conf/ssl.crt/ca-bundle.crt" # Certificate Revocation Lists (CRL): # Set the CA revocation path where to find CA CRLs for client # authentication or alternatively one huge file containing all # of them (file must be PEM encoded). # The CRL checking mode needs to be configured explicitly # through SSLCARevocationCheck (defaults to "none" otherwise). # Note: Inside SSLCARevocationPath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCARevocationPath "${SRVROOT}/conf/ssl.crl" #SSLCARevocationFile "${SRVROOT}/conf/ssl.crl/ca-bundle.crl" #SSLCARevocationCheck chain # Client Authentication (Type): # Client certificate verification type and depth. Types are # none, optional, require and optional_no_ca. Depth is a # number which specifies how deeply to verify the certificate # issuer chain before deciding the certificate is not valid. #SSLVerifyClient require #SSLVerifyDepth 10 # TLS-SRP mutual authentication: # Enable TLS-SRP and set the path to the OpenSSL SRP verifier # file (containing login information for SRP user accounts). # Requires OpenSSL 1.0.1 or newer. See the mod_ssl FAQ for # detailed instructions on creating this file. Example: # "openssl srp -srpvfile ${SRVROOT}/conf/passwd.srpv -add username" #SSLSRPVerifierFile "${SRVROOT}/conf/passwd.srpv" # Access Control: # With SSLRequire you can do per-directory access control based # on arbitrary complex boolean expressions containing server # variable checks and other lookup directives. The syntax is a # mixture between C and Perl. See the mod_ssl documentation # for more details. #<Location /> #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \ # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \ # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \ # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \ # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \ # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ #</Location> # SSL Engine Options: # Set various options for the SSL engine. # o FakeBasicAuth: # Translate the client X.509 into a Basic Authorisation. This means that # the standard Auth/DBMAuth methods can be used for access control. The # user name is the `one line' version of the client's X.509 certificate. # Note that no password is obtained from the user. Every entry in the user # file needs this password: `xxj31ZMTZzkVA'. # o ExportCertData: # This exports two additional environment variables: SSL_CLIENT_CERT and # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the # server (always existing) and the client (only existing when client # authentication is used). This can be used to import the certificates # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment variables. # Per default this exportation is switched off for performance reasons, # because the extraction step is an expensive operation and is usually # useless for serving static content. So one usually enables the # exportation for CGI and SSI requests only. # o StrictRequire: # This denies access when "SSLRequireSSL" or "SSLRequire" applied even # under a "Satisfy any" situation, i.e. when it applies access is denied # and no other module can change it. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire <FilesMatch "\.(cgi|shtml|phtml|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Directory "/xampp/apache/cgi-bin"> SSLOptions +StdEnvVars </Directory> # SSL Protocol Adjustments: # The safe and default but still SSL/TLS standard compliant shutdown # approach is that mod_ssl sends the close notify alert but doesn't wait for # the close notify alert from client. When you need a different shutdown # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i.e. no # SSL close notify alert is sent or allowed to be received. This violates # the SSL/TLS standard but is needed for some brain-dead browsers. Use # this when you receive I/O errors because of the standard approach where # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, i.e. a # SSL close notify alert is send and mod_ssl waits for the close notify # alert of the client. This is 100% SSL/TLS standard compliant, but in # practice often causes hanging connections with brain-dead browsers. Use # this only for browsers where you know that their SSL implementation # works correctly. # Notice: Most problems of broken clients are also related to the HTTP # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable "nokeepalive" for this. # Similarly, one has to force some clients to use HTTP/1.0 to workaround # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and # "force-response-1.0" for this. BrowserMatch "MSIE [2-5]" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 # Per-Server Logging: # The home of a custom SSL log file. Use this when you want a # compact non-error SSL logfile on a virtual host basis. CustomLog "/xampp/apache/logs/ssl_request.log" \ "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" </VirtualHost>

but now all sites going directly to the xampp dashboard, or some of them does not work at all anymore.
i have also copied the complete -old apache-httpd-ssl conf in to the new one.

Hello everyone

"XAMPP 8.X.X is giving me a lot of trouble, including unexpected crashes and module incompatibilities. We're hoping for quick upgrades to fix these issues and improve the platform's overall performance and stability. #SoftwareBugs #XAMPP"

Code: Select all: # # This is the Apache server configuration file providing SSL support. # It contains the configuration directives to instruct the server how to # serve pages over an https connection. For detailed information about these # directives see <URL:http://httpd.apache.org/docs/2.4/mod/mod_ssl.html> # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # Required modules: mod_log_config, mod_setenvif, mod_ssl, # socache_shmcb_module (for default value of SSLSessionCache) # # Pseudo Random Number Generator (PRNG): # Configure one or more sources to seed the PRNG of the SSL library. # The seed data should be of good random quality. # WARNING! On some platforms /dev/random blocks if not enough entropy # is available. This means you then cannot use the /dev/random device # because it would lead to very long connection times (as long as # it requires to make more entropy available). But usually those # platforms additionally provide a /dev/urandom device which doesn't # block. So, if available, use this one instead. Read the mod_ssl User # Manual for more details. # #SSLRandomSeed startup file:/dev/random 512 #SSLRandomSeed startup file:/dev/urandom 512 #SSLRandomSeed connect file:/dev/random 512 #SSLRandomSeed connect file:/dev/urandom 512 # # When we also provide SSL we have to listen to the # standard HTTP port (see above) and to the HTTPS port # Listen 4434 ## ## SSL Global Context ## ## All SSL configuration in this context applies both to ## the main server and all SSL-enabled virtual hosts. ## # SSL Cipher Suite: # List the ciphers that the client is permitted to negotiate, # and that httpd will negotiate as the client of a proxied server. # See the OpenSSL documentation for a complete list of ciphers, and # ensure these follow appropriate best practices for this deployment. # httpd 2.2.30, 2.4.13 and later force-disable aNULL, eNULL and EXP ciphers, # while OpenSSL disabled these by default in 0.9.8zf/1.0.0r/1.0.1m/1.0.2a. SSLCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES SSLProxyCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES # By the end of 2016, only TLSv1.2 ciphers should remain in use. # Older ciphers should be disallowed as soon as possible, while the # kRSA ciphers do not offer forward secrecy. These changes inhibit # older clients (such as IE6 SP2 or IE8 on Windows XP, or other legacy # non-browser tooling) from successfully connecting. # # To restrict mod_ssl to use only TLSv1.2 ciphers, and disable # those protocols which do not support forward secrecy, replace # the SSLCipherSuite and SSLProxyCipherSuite directives above with # the following two directives, as soon as practical. # SSLCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA # SSLProxyCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA # User agents such as web browsers are not configured for the user's # own preference of either security or performance, therefore this # must be the prerogative of the web server administrator who manages # cpu load versus confidentiality, so enforce the server's cipher order. SSLHonorCipherOrder on # SSL Protocol support: # List the protocol versions which clients are allowed to connect with. # Disable SSLv3 by default (cf. RFC 7525 3.1.1). TLSv1 (1.0) should be # disabled as quickly as practical. By the end of 2016, only the TLSv1.2 # protocol or later should remain in use. SSLProtocol all -SSLv3 SSLProxyProtocol all -SSLv3 # Pass Phrase Dialog: # Configure the pass phrase gathering process. # The filtering dialog program (`builtin' is an internal # terminal dialog) has to provide the pass phrase on stdout. SSLPassPhraseDialog builtin # Inter-Process Session Cache: # Configure the SSL Session Cache: First the mechanism # to use and second the expiring timeout (in seconds). #SSLSessionCache "shmcb:E:/xampp/apache/logs/ssl_scache(512000)" SSLSessionCache "shmcb:E:/xampp/apache/logs/ssl_scache(512000)" SSLSessionCacheTimeout 300 # OCSP Stapling (requires OpenSSL 0.9.8h or later) # # This feature is disabled by default and requires at least # the two directives SSLUseStapling and SSLStaplingCache. # Refer to the documentation on OCSP Stapling in the SSL/TLS # How-To for more information. # # Enable stapling for all SSL-enabled servers: #SSLUseStapling On # Define a relatively small cache for OCSP Stapling using # the same mechanism that is used for the SSL session cache # above. If stapling is used with more than a few certificates, # the size may need to be increased. (AH01929 will be logged.) #SSLStaplingCache "shmcb:${SRVROOT}/logs/ssl_stapling(32768)" # Seconds before valid OCSP responses are expired from the cache #SSLStaplingStandardCacheTimeout 3600 # Seconds before invalid OCSP responses are expired from the cache #SSLStaplingErrorCacheTimeout 600 ## ## SSL Virtual Host Context ## <VirtualHost _default_:4434> # General setup for the virtual host DocumentRoot "E:/xampp/htdocs" ServerName www.example.com:4434 ServerAdmin admin@example.com ErrorLog "E:/xampp/apache/logs/error.log" TransferLog "E:/xampp/apache/logs/access.log" # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on # Server Certificate: # Point SSLCertificateFile "conf/ssl.crt/server.crt" # the certificate is encrypted, then you will be prompted for a # pass phrase. Note that a kill -HUP will prompt again. Keep # in mind that if you have both an RSA and a DSA certificate you # can configure both in parallel (to also allow the use of DSA # ciphers, etc.) # Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt) # require an ECC certificate which can also be configured in # parallel. SSLCertificateFile "conf/ssl.crt/server.crt" #SSLCertificateFile "conf/ssl.crt/server.crt" #SSLCertificateFile "conf/ssl.crt/server.crt" # Server Private Key: # If the key is not combined with the certificate, use this # directive to point at the key file. Keep in mind that if # you've both a RSA and a DSA private key you can configure # both in parallel (to also allow the use of DSA ciphers, etc.) # ECC keys, when in use, can also be configured in parallel SSLCertificateKeyFile "conf/ssl.key/server.key" #SSLCertificateKeyFile "conf/ssl.key/server.key" #SSLCertificateKeyFile "conf/ssl.key/server.key" # Server Certificate Chain: # Point SSLCertificateChainFile at a file containing the # concatenation of PEM encoded CA certificates which form the # certificate chain for the server certificate. Alternatively # the referenced file can be the same as SSLCertificateFile "conf/ssl.crt/server.crt" # certificate for convenience. #SSLCertificateChainFile "${SRVROOT}/conf/server-ca.crt" # Certificate Authority (CA): # Set the CA certificate verification path where to find CA # certificates for client authentication or alternatively one # huge file containing all of them (file must be PEM encoded) # Note: Inside SSLCACertificatePath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCACertificatePath "${SRVROOT}/conf/ssl.crt" #SSLCACertificateFile "${SRVROOT}/conf/ssl.crt/ca-bundle.crt" # Certificate Revocation Lists (CRL): # Set the CA revocation path where to find CA CRLs for client # authentication or alternatively one huge file containing all # of them (file must be PEM encoded). # The CRL checking mode needs to be configured explicitly # through SSLCARevocationCheck (defaults to "none" otherwise). # Note: Inside SSLCARevocationPath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCARevocationPath "${SRVROOT}/conf/ssl.crl" #SSLCARevocationFile "${SRVROOT}/conf/ssl.crl/ca-bundle.crl" #SSLCARevocationCheck chain # Client Authentication (Type): # Client certificate verification type and depth. Types are # none, optional, require and optional_no_ca. Depth is a # number which specifies how deeply to verify the certificate # issuer chain before deciding the certificate is not valid. #SSLVerifyClient require #SSLVerifyDepth 10 # TLS-SRP mutual authentication: # Enable TLS-SRP and set the path to the OpenSSL SRP verifier # file (containing login information for SRP user accounts). # Requires OpenSSL 1.0.1 or newer. See the mod_ssl FAQ for # detailed instructions on creating this file. Example: # "openssl srp -srpvfile ${SRVROOT}/conf/passwd.srpv -add username" #SSLSRPVerifierFile "${SRVROOT}/conf/passwd.srpv" # Access Control: # With SSLRequire you can do per-directory access control based # on arbitrary complex boolean expressions containing server # variable checks and other lookup directives. The syntax is a # mixture between C and Perl. See the mod_ssl documentation # for more details. #<Location /> #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \ # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \ # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \ # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \ # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \ # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ #</Location> # SSL Engine Options: # Set various options for the SSL engine. # o FakeBasicAuth: # Translate the client X.509 into a Basic Authorisation. This means that # the standard Auth/DBMAuth methods can be used for access control. The # user name is the `one line' version of the client's X.509 certificate. # Note that no password is obtained from the user. Every entry in the user # file needs this password: `xxj31ZMTZzkVA'. # o ExportCertData: # This exports two additional environment variables: SSL_CLIENT_CERT and # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the # server (always existing) and the client (only existing when client # authentication is used). This can be used to import the certificates # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment variables. # Per default this exportation is switched off for performance reasons, # because the extraction step is an expensive operation and is usually # useless for serving static content. So one usually enables the # exportation for CGI and SSI requests only. # o StrictRequire: # This denies access when "SSLRequireSSL" or "SSLRequire" applied even # under a "Satisfy any" situation, i.e. when it applies access is denied # and no other module can change it. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire <FilesMatch "\.(cgi|shtml|phtml|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Directory "E:/xampp/apache/cgi-bin"> SSLOptions +StdEnvVars </Directory> # SSL Protocol Adjustments: # The safe and default but still SSL/TLS standard compliant shutdown # approach is that mod_ssl sends the close notify alert but doesn't wait for # the close notify alert from client. When you need a different shutdown # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i.e. no # SSL close notify alert is sent or allowed to be received. This violates # the SSL/TLS standard but is needed for some brain-dead browsers. Use # this when you receive I/O errors because of the standard approach where # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, i.e. a # SSL close notify alert is send and mod_ssl waits for the close notify # alert of the client. This is 100% SSL/TLS standard compliant, but in # practice often causes hanging connections with brain-dead browsers. Use # this only for browsers where you know that their SSL implementation # works correctly. # Notice: Most problems of broken clients are also related to the HTTP # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable "nokeepalive" for this. # Similarly, one has to force some clients to use HTTP/1.0 to workaround # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and # "force-response-1.0" for this. BrowserMatch "MSIE [2-5]" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 # Per-Server Logging: # The home of a custom SSL log file. Use this when you want a # compact non-error SSL logfile on a virtual host basis. CustomLog "E:/xampp/apache/logs/ssl_request.log" \ "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" </VirtualHost>

Here, as you command the SSL config.

Here is the httpd.conf configuration .

Code: Select all: # # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See <URL:http://httpd.apache.org/docs/2.4/> for detailed information. # In particular, see # <URL:http://httpd.apache.org/docs/2.4/mod/directives.html> # for a discussion of each configuration directive. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "logs/access_log" # with ServerRoot set to "/usr/local/apache2" will be interpreted by the # server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log" # will be interpreted as '/logs/access_log'. # # NOTE: Where filenames are specified, you must use forward slashes # instead of backslashes (e.g., "c:/apache" instead of "c:\apache"). # If a drive letter is omitted, the drive on which httpd.exe is located # will be used by default. It is recommended that you always supply # an explicit drive letter in absolute paths to avoid confusion. # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # Do not add a slash at the end of the directory path. If you point # ServerRoot at a non-local disk, be sure to specify a local disk on the # Mutex directive, if file-based mutexes are used. If you wish to share the # same ServerRoot for multiple httpd daemons, you will need to change at # least PidFile. # Define SRVROOT "E:/xampp/apache" ServerRoot "E:/xampp/apache" # # Mutex: Allows you to set the mutex mechanism and mutex file directory # for individual mutexes, or change the global defaults # # Uncomment and change the directory if mutexes are file-based and the default # mutex file directory is not on a local disk or is not appropriate for some # other reason. # # Mutex default:logs # # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, instead of the default. See also the <VirtualHost> # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses. # #Listen 12.34.56.78:80 Listen 80 # Disable Trace TraceEnable Off # # Dynamic Shared Object (DSO) Support # # To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule' lines at this location so the # directives contained in it are actually available _before_ they are used. # Statically compiled modules (those listed by `httpd -l') do not need # to be loaded here. # # Example: # LoadModule foo_module modules/mod_foo.so # LoadModule access_compat_module modules/mod_access_compat.so LoadModule actions_module modules/mod_actions.so LoadModule alias_module modules/mod_alias.so LoadModule allowmethods_module modules/mod_allowmethods.so LoadModule asis_module modules/mod_asis.so LoadModule auth_basic_module modules/mod_auth_basic.so #LoadModule auth_digest_module modules/mod_auth_digest.so #LoadModule auth_form_module modules/mod_auth_form.so #LoadModule authn_anon_module modules/mod_authn_anon.so LoadModule authn_core_module modules/mod_authn_core.so #LoadModule authn_dbd_module modules/mod_authn_dbd.so #LoadModule authn_dbm_module modules/mod_authn_dbm.so LoadModule authn_file_module modules/mod_authn_file.so #LoadModule authn_socache_module modules/mod_authn_socache.so #LoadModule authnz_fcgi_module modules/mod_authnz_fcgi.so #LoadModule authnz_ldap_module modules/mod_authnz_ldap.so LoadModule authz_core_module modules/mod_authz_core.so #LoadModule authz_dbd_module modules/mod_authz_dbd.so #LoadModule authz_dbm_module modules/mod_authz_dbm.so LoadModule authz_groupfile_module modules/mod_authz_groupfile.so LoadModule authz_host_module modules/mod_authz_host.so #LoadModule authz_owner_module modules/mod_authz_owner.so LoadModule authz_user_module modules/mod_authz_user.so LoadModule autoindex_module modules/mod_autoindex.so #LoadModule brotli_module modules/mod_brotli.so #LoadModule buffer_module modules/mod_buffer.so #LoadModule cache_module modules/mod_cache.so #LoadModule cache_disk_module modules/mod_cache_disk.so #LoadModule cache_socache_module modules/mod_cache_socache.so #LoadModule cern_meta_module modules/mod_cern_meta.so LoadModule cgi_module modules/mod_cgi.so #LoadModule charset_lite_module modules/mod_charset_lite.so #LoadModule data_module modules/mod_data.so #LoadModule dav_module modules/mod_dav.so #LoadModule dav_fs_module modules/mod_dav_fs.so LoadModule dav_lock_module modules/mod_dav_lock.so #LoadModule dbd_module modules/mod_dbd.so #LoadModule deflate_module modules/mod_deflate.so LoadModule dir_module modules/mod_dir.so #LoadModule dumpio_module modules/mod_dumpio.so LoadModule env_module modules/mod_env.so #LoadModule expires_module modules/mod_expires.so #LoadModule ext_filter_module modules/mod_ext_filter.so #LoadModule file_cache_module modules/mod_file_cache.so #LoadModule filter_module modules/mod_filter.so #LoadModule http2_module modules/mod_http2.so LoadModule headers_module modules/mod_headers.so #LoadModule heartbeat_module modules/mod_heartbeat.so #LoadModule heartmonitor_module modules/mod_heartmonitor.so #LoadModule ident_module modules/mod_ident.so #LoadModule imagemap_module modules/mod_imagemap.so LoadModule include_module modules/mod_include.so LoadModule info_module modules/mod_info.so LoadModule isapi_module modules/mod_isapi.so #LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so #LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so #LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so #LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so #LoadModule ldap_module modules/mod_ldap.so #LoadModule logio_module modules/mod_logio.so LoadModule log_config_module modules/mod_log_config.so #LoadModule log_debug_module modules/mod_log_debug.so #LoadModule log_forensic_module modules/mod_log_forensic.so #LoadModule lua_module modules/mod_lua.so LoadModule cache_disk_module modules/mod_cache_disk.so #LoadModule macro_module modules/mod_macro.so #LoadModule md_module modules/mod_md.so LoadModule mime_module modules/mod_mime.so #LoadModule mime_magic_module modules/mod_mime_magic.so LoadModule negotiation_module modules/mod_negotiation.so LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_ajp_module modules/mod_proxy_ajp.so #LoadModule proxy_balancer_module modules/mod_proxy_balancer.so #LoadModule proxy_connect_module modules/mod_proxy_connect.so #LoadModule proxy_express_module modules/mod_proxy_express.so #LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so #LoadModule proxy_hcheck_module modules/mod_proxy_hcheck.so #LoadModule proxy_html_module modules/mod_proxy_html.so #LoadModule proxy_http_module modules/mod_proxy_http.so #LoadModule proxy_http2_module modules/mod_proxy_http2.so #LoadModule proxy_scgi_module modules/mod_proxy_scgi.so #LoadModule proxy_uwsgi_module modules/mod_proxy_uwsgi.so #LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so #LoadModule ratelimit_module modules/mod_ratelimit.so #LoadModule reflector_module modules/mod_reflector.so #LoadModule remoteip_module modules/mod_remoteip.so #LoadModule request_module modules/mod_request.so #LoadModule reqtimeout_module modules/mod_reqtimeout.so LoadModule rewrite_module modules/mod_rewrite.so #LoadModule sed_module modules/mod_sed.so #LoadModule session_module modules/mod_session.so #LoadModule session_cookie_module modules/mod_session_cookie.so #LoadModule session_crypto_module modules/mod_session_crypto.so #LoadModule session_dbd_module modules/mod_session_dbd.so LoadModule setenvif_module modules/mod_setenvif.so #LoadModule slotmem_plain_module modules/mod_slotmem_plain.so #LoadModule slotmem_shm_module modules/mod_slotmem_shm.so #LoadModule socache_dbm_module modules/mod_socache_dbm.so #LoadModule socache_memcache_module modules/mod_socache_memcache.so #LoadModule socache_redis_module modules/mod_socache_redis.so LoadModule socache_shmcb_module modules/mod_socache_shmcb.so #LoadModule speling_module modules/mod_speling.so LoadModule ssl_module modules/mod_ssl.so LoadModule status_module modules/mod_status.so #LoadModule substitute_module modules/mod_substitute.so #LoadModule unique_id_module modules/mod_unique_id.so #LoadModule userdir_module modules/mod_userdir.so #LoadModule usertrack_module modules/mod_usertrack.so LoadModule version_module modules/mod_version.so #LoadModule vhost_alias_module modules/mod_vhost_alias.so #LoadModule watchdog_module modules/mod_watchdog.so #LoadModule xml2enc_module modules/mod_xml2enc.so <IfModule unixd_module> # # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # # User/Group: The name (or #number) of the user/group to run httpd as. # It is usually good practice to create a dedicated user and group for # running httpd, as with most system services. # User daemon Group daemon </IfModule> # 'Main' server configuration # # The directives in this section set up the values used by the 'main' # server, which responds to any requests that aren't handled by a # <VirtualHost> definition. These values also provide defaults for # any <VirtualHost> containers you may define later in the file. # # All of these directives may appear inside <VirtualHost> containers, # in which case these default settings will be overridden for the # virtual host being defined. # # # ServerAdmin: Your address, where problems with the server should be # e-mailed. This address appears on some server-generated pages, such # as error documents. e.g. admin@your-domain.com # ServerAdmin postmaster@localhost # # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If your host doesn't have a registered DNS name, enter its IP address here. # ServerName localhost:80 # # Deny access to the entirety of your server's filesystem. You must # explicitly permit access to web content directories in other # <Directory> blocks below. # <Directory /> AllowOverride none Require all denied </Directory> # # Note that from this point forward you must specifically allow # particular features to be enabled - so if something's not working as # you might expect, make sure that you have specifically enabled it # below. # # # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # DocumentRoot "E:/xampp/htdocs" <Directory "E:/xampp/htdocs"> # # Possible values for the Options directive are "None", "All", # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that "MultiViews" must be named *explicitly* --- "Options All" # doesn't give it to you. # # The Options directive is both complicated and important. Please see # http://httpd.apache.org/docs/2.4/mod/core.html#options # for more information. # Options Indexes FollowSymLinks Includes ExecCGI # # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords: # AllowOverride FileInfo AuthConfig Limit # AllowOverride All # # Controls who can get stuff from this server. # Require all granted </Directory> # # DirectoryIndex: sets the file that Apache will serve if a directory # is requested. # <IfModule dir_module> DirectoryIndex index.php index.pl index.cgi index.asp index.shtml index.html index.htm \ default.php default.pl default.cgi default.asp default.shtml default.html default.htm \ home.php home.pl home.cgi home.asp home.shtml home.html home.htm </IfModule> # # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <Files ".ht*"> Require all denied </Files> # # ErrorLog: The location of the error log file. # If you do not specify an ErrorLog directive within a <VirtualHost> # container, error messages relating to that virtual host will be # logged here. If you *do* define an error logfile for a <VirtualHost> # container, that host's errors will be logged there and not here. # ErrorLog "logs/error.log" # # LogLevel: Control the number of messages logged to the error_log. # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. # LogLevel warn <IfModule log_config_module> # # The following directives define some format nicknames for use with # a CustomLog directive (see below). # LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%h %l %u %t \"%r\" %>s %b" common <IfModule logio_module> # You need to enable mod_logio.c to use %I and %O LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio </IfModule> # # The location and format of the access logfile (Common Logfile Format). # If you do not define any access logfiles within a <VirtualHost> # container, they will be logged here. Contrariwise, if you *do* # define per-<VirtualHost> access logfiles, transactions will be # logged therein and *not* in this file. # #CustomLog "logs/access.log" common # # If you prefer a logfile with access, agent, and referer information # (Combined Logfile Format) you can use the following directive. # CustomLog "logs/access.log" combined </IfModule> <IfModule alias_module> # # Redirect: Allows you to tell clients about documents that used to # exist in your server's namespace, but do not anymore. The client # will make a new request for the document at its new location. # Example: # Redirect permanent /foo http://www.example.com/bar # # Alias: Maps web paths into filesystem paths and is used to # access content that does not live under the DocumentRoot. # Example: # Alias /webpath /full/filesystem/path # # If you include a trailing / on /webpath then the server will # require it to be present in the URL. You will also likely # need to provide a <Directory> section to allow access to # the filesystem path. # # ScriptAlias: This controls which directories contain server scripts. # ScriptAliases are essentially the same as Aliases, except that # documents in the target directory are treated as applications and # run by the server when requested rather than as documents sent to the # client. The same rules about trailing "/" apply to ScriptAlias # directives as to Alias. # ScriptAlias /cgi-bin/ "E:/xampp/cgi-bin/" </IfModule> <IfModule cgid_module> # # ScriptSock: On threaded servers, designate the path to the UNIX # socket used to communicate with the CGI daemon of mod_cgid. # #Scriptsock cgisock </IfModule> # # "E:/xampp/cgi-bin" should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # <Directory "E:/xampp/cgi-bin"> AllowOverride All Options None Require all granted </Directory> <IfModule headers_module> # # Avoid passing HTTP_PROXY environment to CGI's on this or any proxied # backend servers which have lingering "httpoxy" defects. # 'Proxy' request header is undefined by the IETF, not listed by IANA # RequestHeader unset Proxy early </IfModule> <IfModule mime_module> # # TypesConfig points to the file containing the list of mappings from # filename extension to MIME-type. # TypesConfig conf/mime.types # # AddType allows you to add to or override the MIME configuration # file specified in TypesConfig for specific file types. # #AddType application/x-gzip .tgz # # AddEncoding allows you to have certain browsers uncompress # information on the fly. Note: Not all browsers support this. # #AddEncoding x-compress .Z #AddEncoding x-gzip .gz .tgz # # If the AddEncoding directives above are commented-out, then you # probably should define those extensions to indicate media types: # AddType application/x-compress .Z AddType application/x-gzip .gz .tgz # # AddHandler allows you to map certain file extensions to "handlers": # actions unrelated to filetype. These can be either built into the server # or added with the Action directive (see below) # # To use CGI scripts outside of ScriptAliased directories: # (You will also need to add "ExecCGI" to the "Options" directive.) # AddHandler cgi-script .cgi .pl .asp # For type maps (negotiated resources): #AddHandler type-map var # # Filters allow you to process content before it is sent to the client. # # To parse .shtml files for server-side includes (SSI): # (You will also need to add "Includes" to the "Options" directive.) # AddType text/html .shtml AddOutputFilter INCLUDES .shtml </IfModule> # # The mod_mime_magic module allows the server to use various hints from the # contents of the file itself to determine its type. The MIMEMagicFile # directive tells the module where the hint definitions are located. # <IfModule mime_magic_module> # # The mod_mime_magic module allows the server to use various hints from the # contents of the file itself to determine its type. The MIMEMagicFile # directive tells the module where the hint definitions are located. # MIMEMagicFile "conf/magic" </IfModule> # # Customizable error responses come in three flavors: # 1) plain text 2) local redirects 3) external redirects # # Some examples: #ErrorDocument 500 "The server made a boo boo." #ErrorDocument 404 /missing.html #ErrorDocument 404 "/cgi-bin/missing_handler.pl" #ErrorDocument 402 http://www.example.com/subscription_info.html # # # MaxRanges: Maximum number of Ranges in a request before # returning the entire resource, or one of the special # values 'default', 'none' or 'unlimited'. # Default setting is to accept 200 Ranges. #MaxRanges unlimited # # EnableMMAP and EnableSendfile: On systems that support it, # memory-mapping or the sendfile syscall may be used to deliver # files. This usually improves server performance, but must # be turned off when serving from networked-mounted # filesystems or if support for these functions is otherwise # broken on your system. # Defaults: EnableMMAP On, EnableSendfile Off # #EnableMMAP off #EnableSendfile off # Supplemental configuration # # The configuration files in the conf/extra/ directory can be # included to add extra features or to modify the default configuration of # the server, or you may simply copy their contents here and change as # necessary. # Server-pool management (MPM specific) Include conf/extra/httpd-mpm.conf # Multi-language error messages #Include conf/extra/httpd-multilang-errordoc.conf # Fancy directory listings Include conf/extra/httpd-autoindex.conf # Language settings Include conf/extra/httpd-languages.conf # User home directories Include conf/extra/httpd-userdir.conf # Real-time info on requests and configuration Include conf/extra/httpd-info.conf # Virtual hosts Include conf/extra/httpd-vhosts.conf # Local access to the Apache HTTP Server Manual #Include conf/extra/httpd-manual.conf # Distributed authoring and versioning (WebDAV) #Attention! WEB_DAV is a security risk without a new userspecific configuration for a secure authentifcation #Include conf/extra/httpd-dav.conf # Various default settings #Include conf/extra/httpd-default.conf # Implements a proxy/gateway for Apache. Include "conf/extra/httpd-proxy.conf" # Various default settings Include "conf/extra/httpd-default.conf" # XAMPP settings Include "conf/extra/httpd-xampp.conf" # Configure mod_proxy_html to understand HTML4/XHTML1 <IfModule proxy_html_module> Include conf/extra/proxy-html.conf </IfModule> # Secure (SSL/TLS) connections Include conf/extra/httpd-ssl.conf # # Note: The following must must be present to support # starting without SSL on platforms with no /dev/random equivalent # but a statically compiled-in mod_ssl. # <IfModule ssl_module> SSLRandomSeed startup builtin SSLRandomSeed connect builtin </IfModule> # XAMPP: We disable operating system specific optimizations for a listening # socket by the http protocol here. IE 64 bit make problems without this. AcceptFilter http none AcceptFilter https none # AJP13 Proxy <IfModule mod_proxy.c> <IfModule mod_proxy_ajp.c> Include "conf/extra/httpd-ajp.conf" </IfModule> </IfModule>

Apache Friends Support Forum

Search found 1099 matches: performance

die WordPress 6.6: aktuelle Arbeiten am zweiten Majorrelease

Improving Website Performance: My Journey with PHP and MySQL

Re: Trying to Learn + Test SSL Setup

Neu: WordPress Version 6.5. erste Major release: viel Neues!

WordPress and Notion: some ways and methods to interact

Optimizing PHP Performance for My XAMPP Environment

OBS Studio 30.1 Beta released mit AV1 Support usw. usf

ArchBang, Dog, Puppy, DammnedSmall and other light Linuxes

Re: When will there be a working version XAMPP?

a lightweight linux distro for a older Hardware ideas...!?

SQL database / table on multiple hard disks possible?

Re: downgrading php version not going as expected

Re: [BUGS] Known XAMPP 8.X.X issues

Re: downgrading php version not going as expected

Re: downgrading php version not going as expected