Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] migration woes from version 9 to 10 - possible character encoding issue
  • From: Bryan Coleman <bryan.coleman@xxxxxxxx>
  • Date: Thu, 18 Aug 2022 11:50:18 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=dart.biz; dmarc=pass action=none header.from=dart.biz; dkim=pass header.d=dart.biz; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=XBu0KyeA3Pca/edNxHYOY6gUnjac+8pXKQBzQzEN3jk=; b=PNCZtzyU16krSoL9yKJPZSJZTmTYiMSXNjMxqkWtzB8Ac4mtildTeVTMMhyNEklWy9uvS9HW0OCOc/+7m+kopsw91vQ5PPSnCWowKMkaYPhBuYrRzhEZCDEGqTAnBWOEOrRZT/Xi6CTEXTylv4fZlW4MWH2/rs/3K0oChY6D/KiPNlaVdYJWagGUerU/A3j7JPnv69jeH+jjNrmaYylDryuk/Fvq8ZAq8MG6KL/66vCW2PrgJfDwsEjSaMBcL+GgXBhACXAA0gOpfsDIWRmwNwwH566+fuz6Vy3OyfikOCSuGLVoSNomxTee6BKRwgJfCHKStp/wh9rLeFSUhD9tlw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=h+67CVkm77Vmo7pvEZMp5zUktdb5rz+qbIdYwc/owYSE931pfgCYPNS8SMZhOLEwHglmbWqMZooAAMRSg3y4hzDbZ5PB8IhNeQNw+J/r/AdZaXelhjGr6n2JKJTyLvBTJdDQtyH8MZq5GGIeNsFmEvnbKqJXtMWUEb1/1Fm/iKJ6Lgbdan7zYa2vBBO5ZyM9ESnnnP/xiM0I5beedXPSmI3DCMV4OAtx9b5MwDdt/1gIehPU1nUnQrZ600zwRMPQaZuGTmyTd6g1V9ZVdi+qg3a/CrQ24G5VtYnST1N0eU4DOoBbEo11Z2Aqo4HebogkWy49vUkh+cqjuAqZCf913w==
  • Delivered-to: jetty-users@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/jetty-users/>
  • List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHYsjLBBXbI7TDmsEykBqBgXPJjta20JhwAgABlL/A=
  • Thread-topic: [jetty-users] migration woes from version 9 to 10 - possible character encoding issue

Thanks for the suggestion.  

I tried adding it with no apparent change.  At this point, I am not 100% sure that the encoding is the problem; however, it is the thing that jumped out a me when digging into the issue.  The hunt continues....

Have a great day!
Bryan

-----Original Message-----
From: jetty-users <jetty-users-bounces@xxxxxxxxxxx> On Behalf Of Matthias Pfau via jetty-users
Sent: Thursday, August 18, 2022 1:42 AM
To: Bryan Coleman via jetty-users <jetty-users@xxxxxxxxxxx>
Cc: Matthias Pfau <matthias.pfau@xxxxxxxx>
Subject: Re: [jetty-users] migration woes from version 9 to 10 - possible character encoding issue

I think JVM picks up the systems default encoding if you don't override it. Did you try setting default encoding to UTF-8 by passing JVM arg at startup (-Dfile.encoding=UTF-8)?

Best,
Matthias

Aug 17, 2022, 14:13 by jetty-users@xxxxxxxxxxx:

>
> I am working to migrate a project codebase from jetty version 9.4.46 to version 10.0.11.  The set up is an embedded servlet with Kerberos authentication and works just fine when running from an IDE; however, when running it from an uber jar things go south.  When running on the working system with the jar (instead of IDE), a "HTTP Error 401 Unauthorized" response is returned; however, when running on a different system (with jar) a GSSException Invalid argument 400 - cannot find key of appropriate-type to decrypt is returned.  After comparing debug messages, the difference that jumps out is the Content-Type.  For the instance that works, the type is listed as "text/html;charset=utf-8".  For the two that do not work, it is "text/html;charset=iso-8859-1".  My suspicion is that the jar has something missing or misplaced.  That said, I did verify that the encoding.properties file existed and the contents matched those of the working one.
>
>
>  
>
>
> Any clues to where to look next?>  
>
>
>  
>
>
> Is there a global way to force jetty to use UTF-8?  If not global, some other way?  (Thought is that taking that approach could possibly quickly verify my hunch)
>
>
>  
>
>
> Thank you ahead of time for your time and suggestions!
>
>

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eclipse.org%2Fmailman%2Flistinfo%2Fjetty-users&amp;data=05%7C01%7Cbryan.coleman%40dart.biz%7Ce24f5051ebf44dba11bc08da80dc6873%7Cd90804aba2264b3da37a256f7aba7ff1%7C0%7C0%7C637963981406912230%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=DCuFshfYKfaElwX9TCzAUdd63J2g1qN9rydKoxqCDfE%3D&amp;reserved=0


Back to the top