On Wednesday 25 Jun 2014 19:54:51 Joseph wrote: > On 06/25/14 18:30, Mick wrote: > >On Wednesday 25 Jun 2014 17:42:01 Joseph wrote: > >> On 06/24/14 17:25, walt wrote: > >> >On 06/24/2014 08:25 AM, Joseph wrote: > >> >> On 06/23/14 18:08, Mick wrote: > >> >>> On Sunday 22 Jun 2014 22:52:40 Joseph wrote: > >> >>>> I run a server and have two firefox profiles. > >> >>>> I have ssl enabled. > >> >>>> > >> >>>> When I open one profile I it opens my web-page in "https" instead > >> >>>> of "http" When I open another profile it open my webpage in http > >> >>>> > >> >>>> Why is first profile forcing my opening my servers page in https > >> >>>> mode? > >> >>> > >> >>> Has one profile cached and different protocol+URL in the address > >> >>> bar, than the other? > >> >>> > >> >>> Does this persist if you clear the history of the profile? > >> >>> -- > >> >>> Regards, > >> >>> Mick > >> >> > >> >> No, it makes no difference. I cleared history and cache. > >> >> It still tries to open my server page as https instead of http. > >> > > >> >Different profiles can have different firefox add-ons enabled. Might > >> >be worth comparing the list of add-ons in each profile. > >> > > >> >You can also run firefox -safe-mode to disable extensions and see if it > >> >makes any difference. > >> > >> I don't have any plug-in installed; so I'm puzzled by this behavior. > > > >Do your settings for session-cookies differ between the two profiles? > > > >Otherwise I'm running out of ideas. > > Cookies are the same on both profiles "allow for session" > I'm running out of ideas as well.
Logically, the server gets a 'GET / HTTP/1.1' request from the client and responds to it in the same way, irrespective of the client. If you are running some clever authentication and javascript/php on the server, then the request could be tested for the browser capabilities and serve different page content accordingly. Do you see a difference in the initial exchange of: GET / HTTP/1.1 --> HTTP/1.1 200 OK <-- when you use 'tcpflow -c -i eth0' between the two profiles? Note if the browser starts an TLS negotiation then all the content will be encrypted. Otherwise you should be able to see what attributes it sends to the server, e.g. Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 and what the server responds in each case. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
