WFS: WFS Service in EPSG:4326, but bbox using local coordinate system is used

[eri-blan]

Describe the bug
I noticed that for us, when a WFS layer is setup using EPSG:4326 (had to be since it is the only coordinate system available for the service) or perhaps any other than the coordinate system of the map (?), requests to the WFS service (GetFeature) uses for instance in our case EPSG:3009 coordinates for the bbox parameter, resulting in an error.

Using latest develop.

[jacobwod]

Could you please do a quick test with this setup and see if it only occurs when the WFS service's layer is in 4326? This should happen for other projections as well, as soon as they differ from your map's projection. What happens if you use a WFS set in 3006 in your 3009 map?

[eri-blan]

Could you please do a quick test with this setup and see if it only occurs when the WFS service's layer is in 4326? This should happen for other projections as well, as soon as they differ from your map's projection. What happens if you use a WFS set in 3006 in your 3009 map?

Seems to work when i test this but i suspect it has to do with the fact that the service i´m testing has both 3006 and 3009 available as possible projections. The service that only has EPSG:4326 available I suppose can´t handle a bounding box in for example 3009. The request bbox parameter specifies which projection the bbox is given for like bbox=x,y,EPSG:3009