<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>php Archives - blog.icod.de</title>
	<atom:link href="https://blog.icod.de/tag/php/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.icod.de/tag/php/</link>
	<description>Webentwicklung und sonstiger Unsinn :) Web development and other nonsense :)</description>
	<lastBuildDate>Tue, 02 May 2023 10:19:36 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://blog.icod.de/wp-content/uploads/2017/04/darko-luketic-foto.256x256-150x150.jpg</url>
	<title>php Archives - blog.icod.de</title>
	<link>https://blog.icod.de/tag/php/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>upstream sent too big header while reading response header from upstream</title>
		<link>https://blog.icod.de/2023/05/02/upstream-sent-too-big-header-while-reading-response-header-from-upstream/</link>
					<comments>https://blog.icod.de/2023/05/02/upstream-sent-too-big-header-while-reading-response-header-from-upstream/#respond</comments>
		
		<dc:creator><![CDATA[Darko Luketic]]></dc:creator>
		<pubDate>Tue, 02 May 2023 10:19:36 +0000</pubDate>
				<category><![CDATA[Entwicklung]]></category>
		<category><![CDATA[fastcgi]]></category>
		<category><![CDATA[fcgi]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[php]]></category>
		<guid isPermaLink="false">https://blog.icod.de/?p=1903</guid>

					<description><![CDATA[<p>If you&#8217;re getting this error message &#8220;upstream sent too big header while reading response header from upstream&#8221; in the nginx error log and are using fcgi, in my case I was running a PHP script via PHP FPM 8.2 and received a 502 response from nginx. I fixed the issue. Previously I had this nginx&#8230;</p>
<p>The post <a href="https://blog.icod.de/2023/05/02/upstream-sent-too-big-header-while-reading-response-header-from-upstream/">upstream sent too big header while reading response header from upstream</a> appeared first on <a href="https://blog.icod.de">blog.icod.de</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.icod.de/2023/05/02/upstream-sent-too-big-header-while-reading-response-header-from-upstream/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Crayon Syntax Highlighter Updated for PHP 8</title>
		<link>https://blog.icod.de/2021/11/29/crayon-syntax-highlighter-updated-for-php-8/</link>
					<comments>https://blog.icod.de/2021/11/29/crayon-syntax-highlighter-updated-for-php-8/#respond</comments>
		
		<dc:creator><![CDATA[Darko Luketic]]></dc:creator>
		<pubDate>Mon, 29 Nov 2021 00:08:47 +0000</pubDate>
				<category><![CDATA[Allgemein]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[wordpress]]></category>
		<guid isPermaLink="false">https://blog.icod.de/?p=1632</guid>

					<description><![CDATA[<p>I have updated the Crayon Syntax Highlighter to work with PHP8 and above. While I have tagged the release as 2.8.6 I&#8217;m moving away from that version scheme. [crayon-69c8a8ddaaff5558055886/] and use master branch. Remember to visit the settings page and save your settings, especially when switching PHP versions. To my knowledge this is the only&#8230;</p>
<p>The post <a href="https://blog.icod.de/2021/11/29/crayon-syntax-highlighter-updated-for-php-8/">Crayon Syntax Highlighter Updated for PHP 8</a> appeared first on <a href="https://blog.icod.de">blog.icod.de</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.icod.de/2021/11/29/crayon-syntax-highlighter-updated-for-php-8/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Symfony2 File Upload with Related Entities</title>
		<link>https://blog.icod.de/2013/04/17/symfony2-file-upload-with-related-entities/</link>
					<comments>https://blog.icod.de/2013/04/17/symfony2-file-upload-with-related-entities/#comments</comments>
		
		<dc:creator><![CDATA[Darko Luketic]]></dc:creator>
		<pubDate>Wed, 17 Apr 2013 10:16:28 +0000</pubDate>
				<category><![CDATA[Entwicklung]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[symfony]]></category>
		<guid isPermaLink="false">http://blog.icod.de/?p=51</guid>

					<description><![CDATA[<p>This is for a very old version of Symfony &#8211; 2.3 It might not work with the version of Symfony you&#8217;re using Here is how I do it. What it does? Upload an image file and an audio file and add an encode job. The purpose is to join an image and a mp3 into&#8230;</p>
<p>The post <a href="https://blog.icod.de/2013/04/17/symfony2-file-upload-with-related-entities/">Symfony2 File Upload with Related Entities</a> appeared first on <a href="https://blog.icod.de">blog.icod.de</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.icod.de/2013/04/17/symfony2-file-upload-with-related-entities/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
