| 1 |
On Wednesday 25 Jun 2014 19:54:51 Joseph wrote: |
| 2 |
> On 06/25/14 18:30, Mick wrote: |
| 3 |
> >On Wednesday 25 Jun 2014 17:42:01 Joseph wrote: |
| 4 |
> >> On 06/24/14 17:25, walt wrote: |
| 5 |
> >> >On 06/24/2014 08:25 AM, Joseph wrote: |
| 6 |
> >> >> On 06/23/14 18:08, Mick wrote: |
| 7 |
> >> >>> On Sunday 22 Jun 2014 22:52:40 Joseph wrote: |
| 8 |
> >> >>>> I run a server and have two firefox profiles. |
| 9 |
> >> >>>> I have ssl enabled. |
| 10 |
> >> >>>> |
| 11 |
> >> >>>> When I open one profile I it opens my web-page in "https" instead |
| 12 |
> >> >>>> of "http" When I open another profile it open my webpage in http |
| 13 |
> >> >>>> |
| 14 |
> >> >>>> Why is first profile forcing my opening my servers page in https |
| 15 |
> >> >>>> mode? |
| 16 |
> >> >>> |
| 17 |
> >> >>> Has one profile cached and different protocol+URL in the address |
| 18 |
> >> >>> bar, than the other? |
| 19 |
> >> >>> |
| 20 |
> >> >>> Does this persist if you clear the history of the profile? |
| 21 |
> >> >>> -- |
| 22 |
> >> >>> Regards, |
| 23 |
> >> >>> Mick |
| 24 |
> >> >> |
| 25 |
> >> >> No, it makes no difference. I cleared history and cache. |
| 26 |
> >> >> It still tries to open my server page as https instead of http. |
| 27 |
> >> > |
| 28 |
> >> >Different profiles can have different firefox add-ons enabled. Might |
| 29 |
> >> >be worth comparing the list of add-ons in each profile. |
| 30 |
> >> > |
| 31 |
> >> >You can also run firefox -safe-mode to disable extensions and see if it |
| 32 |
> >> >makes any difference. |
| 33 |
> >> |
| 34 |
> >> I don't have any plug-in installed; so I'm puzzled by this behavior. |
| 35 |
> > |
| 36 |
> >Do your settings for session-cookies differ between the two profiles? |
| 37 |
> > |
| 38 |
> >Otherwise I'm running out of ideas. |
| 39 |
> |
| 40 |
> Cookies are the same on both profiles "allow for session" |
| 41 |
> I'm running out of ideas as well. |
| 42 |
|
| 43 |
Logically, the server gets a 'GET / HTTP/1.1' request from the client and |
| 44 |
responds to it in the same way, irrespective of the client. If you are |
| 45 |
running some clever authentication and javascript/php on the server, then the |
| 46 |
request could be tested for the browser capabilities and serve different page |
| 47 |
content accordingly. |
| 48 |
|
| 49 |
Do you see a difference in the initial exchange of: |
| 50 |
|
| 51 |
GET / HTTP/1.1 --> |
| 52 |
|
| 53 |
HTTP/1.1 200 OK <-- |
| 54 |
|
| 55 |
when you use 'tcpflow -c -i eth0' between the two profiles? |
| 56 |
|
| 57 |
Note if the browser starts an TLS negotiation then all the content will be |
| 58 |
encrypted. Otherwise you should be able to see what attributes it sends to |
| 59 |
the server, e.g. |
| 60 |
|
| 61 |
Accept: |
| 62 |
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 |
| 63 |
|
| 64 |
and what the server responds in each case. |
| 65 |
|
| 66 |
-- |
| 67 |
Regards, |
| 68 |
Mick |
Archives