Ok now on laptop, so hopefully this will make more sense.
So the first issue is that I would generally put something on the root of the domain. ;So instead of redirecting to /el or /en I'd put the EL content in the root and then redirect users to /en with a 302 if their language/location matches that site. ;Redirecting for language detection should always be with <b>302</b>.
Next item is redirecting all www traffic to non-www. ;This should be done with a <b>301</b>. ;So in the case of a EN user visiting they will first be 301 redirected to ; and then 302 redirected to ;
Whether you do these redirects in .htaccess or header include is up to you, but doing them all via .htaccess will speed things up for your users.
www-<del>>301-</del>>non www-<del>>301-</del>> non www (el) ; ; ; ; ; ; and -->non www-<del>>302-</del>> non www (en) all via htaccess. ; Correct? Can the same page have a 301 and 302 redirect? ; Thank you again for your help
Richard Hearne: If you want to keep your content in the current folders:
All requests for www get 301'd to their non-www equivalents All language based redirects are 302
So yes, a single request could result in booth a 301 and a subsequent 302.
But I still suggest you move EN or EL to the root folder. If not then you're going to have to serve 301s to whichever language is your homepage.
Tbh the real mistake here is that you have no clear homepage.